Related
My xda 2 is stuck on the bootloader and wont do anything after trying to reset it ive tried i think everything that i can possible do and i read most of what was offered yet its still stuck on the bootloader. I tried to upgrade from v1.60.... to the latest at v1.72.187 uk o2 . Please help ><
Have you tried resetting your device, placing it back in the cradle and re-running the upgrade?
I have tried reseting but it fades then reappears disallowing me to run the upgrade 'Xda_II_172187_Final' but i have downloaded another which sizes around 512kb but this says that the rom image is not present. :/ can u link me to another upgrade if it may help
Shadow786 said:
I have tried reseting but it fades then reappears disallowing me to run the upgrade 'Xda_II_172187_Final' but i have downloaded another which sizes around 512kb but this says that the rom image is not present. :/ can u link me to another upgrade if it may help
Click to expand...
Click to collapse
Exactly which upgrades have you attempted? What happens when you run the XDA_II_172187_Final upgrade?
What is the 512kb upgrade you mention?
I used 'himaupgradeut_197.exe' after the 'Xda_II_172187_Final'.
'himaupgradeut_197.exe' was the 500kb file which gave me the error
that no rom image was found and the 'Xda_II_172187_Final' was the only 1 that i used to upgrade and that says it cannot connect to the device ...make sure its connected.
Shadow786 said:
I used 'himaupgradeut_197.exe' after the 'Xda_II_172187_Final'.
'himaupgradeut_197.exe' was the 500kb file which gave me the error
that no rom image was found and the 'Xda_II_172187_Final' was the only 1 that i used to upgrade and that says it cannot connect to the device ...make sure its connected.
Click to expand...
Click to collapse
The HimaUpgradeUt_197.exe file is not an upgrade it is a version of the upgrade program. It still needs to be used with all the other files that form part of the upgrade process.
As regards the connection error, make sure you are in bootloader mode (by pressing Jog button and Power button at the same time as pressing reset) before retrying the upgrade. Also make sure the USB cradle is plugged directly into a USB port on your PC and not through a hub and that the power supply is connected to the cradle. It may help to make sure that ActiveSync isn't running also, as it is not required for upgrading.
Isnt it already in bootload mode? if not i dont know where the jog button is Also i just realised i didnt have my cradle its own powersuplly which i have done just now but i dont want to carry on witht upgrade is there a way i can just make it back to normal ?
Shadow786 said:
Isnt it already in bootload mode? if not i dont know where the jog button is Also i just realised i didnt have my cradle its own powersuplly which i have done just now but i dont want to carry on witht upgrade is there a way i can just make it back to normal ?
Click to expand...
Click to collapse
It sounds like your device is already in bootloader mode - my suggestion is just a 'failsafe' The Jog button is the multi-directional button at the bottom centre of your device.
I don't think it is possible to 'go back' to normal as if you never did anything. With the power connected properly there is every chance an upgrade will now work. You can, of course upgrade using the original ROM version, if you know what that was.
hmm its still done a restart and yet it doesent seem to connect. When i restart the xda 2 its still in bootload mode when i place it in cradle still in bootload mode and i still get the same errors witht the upgrade ><
OK. This should work Can you try a different USB port? Failing that, is it possible to try another PC? I know about other users that had connection problems and tried a different PC and it worked OK.
Omg thank you i thought i lost it Thank you Very much i cnt thank you enough. ^^
For reference i switched the USB cable around and it worked ^^
That is great news
Ok, so after scanning through the SBF thread and a few others and finding instructions all over the place, I decided to bring them all together in one post. Sorry if I don’t mention everybody that contributed these instructions by name but there were a lot of instructions on how to flash the SBF to our phone. You know who you are and I personally thank you and believe everybody else does also.
To begin, download the necessary files and drivers:
Froyo 2.2.2 SBF File
Gingerbread 2.3.3 SBF File
Gingerbread 2.3.4 SBF File
RSD Lite 5.3.1 and Drivers
RSD Lite 5.4.4
1. Reboot your computer and your phone after downloading and installing everything and before you go to flash the SBF file. Use 7-zip to extract the SBF file...
2. Once you have rebooted your computer, go ahead and start RSD Lite and point it at the SBF file and plug your USB cable into your computer ONLY!
3. Turn your phone off.
4. Turn the phone on by pressing and holding the POWER AND VOLUME DOWN buttons until you see FASTBOOT. Press volume down until you reach RSD and press volume up once.
5. Plug your phone into your computer and wait until you see it in RSD Lite and click Start.
6. Your phone will reboot when the process is complete. DO NOT UNPLUG YOUR PHONE FROM UNTIL THE COMPUTER UNTIL THE PROCESS IS COMPLETE.
7. If the phone boot loops pull the battery and boot into the stock recovery by pressing and holding power and volume down until the phone says FASTBOOT, once the phone says FASTBOOT, press volume down until you see ANDROID RECOVERY, once you see ANDROID RECOVERY, press BOTH the volume up and the volume down buttons. You will see the familiar triangle with the exclamation point and the Android. At this point press volume up and down simultaneously again and select “wipe data/factory data reset” by pressing the power button.
8. Reboot your phone and you should be back to full factory default, like new out of the box.
If you have any other problem with RSD Lite, try running it as administrator in Win 7/Vista...
Thank you, very helpful and thanks to everyone involved. Let's get this ball Rollin baby!
Sent from my DROID X2 with that v6 son using XDA Premium App with
You first link does not work properly. I found a working link in the SBF thread and wanted to confirm that it's 482mb?
Don't actually remember... But I believe so.. I will update the link sortly thanks tho...
EDIT: Yes it is 482MB Link has also been updated...
Sent from my DROID X2 using Tapatalk
Thanks for putting every thing together and thanks to everyone who contributed. This should make it easy for everyone to understand.
Sent from my DROID X2 using XDA Premium App
Added to the roll up sticky, thanks.
Mr. Clown said:
Added to the roll up sticky, thanks.
Click to expand...
Click to collapse
Thank You! Mr. Clown!!! I have been trolling xda since my A&TT Tilt and have become very involved with this phone and am glad to actually help and contribute!!
any guide as to how to unpack the .sbf and reveal its contents
slowz3r said:
any guide as to how to unpack the .sbf and reveal its contents
Click to expand...
Click to collapse
That is actually a great question Slowz3r.... I would love to know how to open that SBF, but I really have no clue... I will try and see if maybe I can open it in Linux. If anybody around here has any ideas or has already tried this, please let me know...
TIA
I have followed this guide to the letter, even to the point of redownloading both the SBF and the drivers a few times. Even after a reboot, when I plug my phone into the computer it says "Unable to retrieve initialization values from INI file"
I've tried it every day for the past 3 and to no avail, always same issue.
Edit: I did a clean uninstall and reinstall of everything, rebooted, and it worked. So I suppose it was an installation error of sorts.
Anyone else notice that to the right under platform it says 4G Tegra? Some also stated that their computer detected a 4G Modem when the phone was in a certain mode.
uhh186 said:
I have followed this guide to the letter, even to the point of redownloading both the SBF and the drivers a few times. Even after a reboot, when I plug my phone into the computer it says "Unable to retrieve initialization values from INI file"
I've tried it every day for the past 3 and to no avail, always same issue.
Edit: I did a clean uninstall and reinstall of everything, rebooted, and it worked. So I suppose it was an installation error of sorts.
Click to expand...
Click to collapse
Believe it or not I, of all people(the person writing the tutorial), had the same issue last night.... I just reinstalled like you said and all worked fine....
zakth said:
Anyone else notice that to the right under platform it says 4G Tegra? Some also stated that their computer detected a 4G Modem when the phone was in a certain mode.
Click to expand...
Click to collapse
Yes, I have also seen this in the options before you get to rsd mode... Don't know what that means or why its labelled that way but it is definitely interesting... It would be great to find out what motorola might have to say about this and if that may be why we have been waiting so long for an update!!! I highly doubt it tho, but still nice to think about...
uhh186 said:
I have followed this guide to the letter, even to the point of redownloading both the SBF and the drivers a few times. Even after a reboot, when I plug my phone into the computer it says "Unable to retrieve initialization values from INI file"
I've tried it every day for the past 3 and to no avail, always same issue.
Edit: I did a clean uninstall and reinstall of everything, rebooted, and it worked. So I suppose it was an installation error of sorts.
Click to expand...
Click to collapse
This happened to me also, i found out after two hours of forum searching, that you need 5.3 rsd lite, the one in the download worked for me, but maybe its your operating system, i had to use my xp computer because it would not work on my Win. 7 machine. Hope this helps.
gageoliver said:
This happened to me also, i found out after two hours of forum searching, that you need 5.3 rsd lite, the one in the download worked for me, but maybe its your operating system, i had to use my xp computer because it would not work on my Win. 7 machine. Hope this helps.
Click to expand...
Click to collapse
It should work with Win 7 as that is what I am running... The link I have posted for rsd lite is 5.3... Maybe if you run rsd lite as admin??? I didn't have to but that might be a solution....
It Works!!
This is the first Sbf download that worked for me, i noticed that this one was over 700 mb in size. All the other ones were 482 mb. I guess those were just the partial Sbf. Thanks for this, i really needed it!
I had to do a factory reset of my phone the other day. I used RSD5.3.1 and the 482 mb SBF.
I bootlooped initially on the reboot but after doing a battery pull and then going into recovery, everything worked. I did get a couple settings wrong on setting up the phone but fortunately, there is a Verizon store very close by.
All the bloatware that TB had backed up up prior to me uninstalling came back. After the reload, I re-rooted but haven't uninstalled or frozen anything yet.
gageoliver said:
This is the first Sbf download that worked for me, i noticed that this one was over 700 mb in size. All the other ones were 482 mb. I guess those were just the partial Sbf. Thanks for this, i really needed it!
Click to expand...
Click to collapse
Actually the sbf included here is also 482 mb... Maybe the other downloads got corrupted?? However, I'm just glad it worked for you!
DAG425 said:
Actually the sbf included here is also 482 mb... Maybe the other downloads got corrupted?? However, I'm just glad it worked for you!
Click to expand...
Click to collapse
New Links I Just Uploaded Yesterday.
http://www.droidforums.net/forum/droid-x2-hacks/156070-sbf-file-rsd-lite-drivers-instructions.html
ok, just sbf'd my phone... hooked up rebooted blah blah blah... now im ****ting my pants... rsd says Results Fail and in the status says Disconnected.... idk why... all i know is that it was up for like the first phase... rebooted and says switchin ti BP mode... did that... then rebooted at 99% and then this.....
Phone is stuck on Moto Dual Core screen... and doing nothing... some please tell me i didnt mess this up.
Edit: Ok, i rebooted did the recovery thing and data wiped, got it working and now configuring the phone.. sorry for this post, was jus scared i guess >.<
I followed the instructions provided at the MEGA UNBRICK something thread situated here http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108/
Anyway, when I hold the volume-up button for 10 seconds, followed by plugging the Onyx with the PC, the system does't detect the device. What can I do now? And is there any alternative method to unbrick a hardbricked phone? I urgently need help
If you installed the drivers and the computer is not reckognizing the device, that's bad news. How did you manage to accomplish that?
aredpanda said:
If you installed the drivers and the computer is nota reckognizing the device, that's bad news. How did you manage to accomplish that?
Click to expand...
Click to collapse
I don't know. And ijust in case if you were being sarcastic, I used the same computer to replace the recovery of this phone.
Im not being sarcastic. The problem with the Android modding scene is that people got too used to blindly following steps without really knowing how they are affecting their devices. In order to get better chances at getting help, you'll need to describe what and exactly how you were altering your phone.
aredpanda said:
Im not being sarcastic. The problem with the Android modding scene is that people got too used to blindly following steps without really knowing how they are affecting their devices. In order to get better chances at getting help, you'll need to describe what and exactly how you were altering your phone.
Click to expand...
Click to collapse
I was using Bliss ROM with BluSpark kernel. Anyway, I downloaded 2 ROMS today, Sailfish OS and the stock H2OS for OPX. I wiped the phone and first flashed the Sailfish OS, but the phone was stuck in a bootloop which only was showing the oneplus logo and the text "Powered by Anrdoid". After that, I entered recovery, and did the normal pre-flash wipe again. This time I flashed the H2OS, but after I gave "Reboot to System", my phone just wont do nor display anything. Hardbricked, dead
Can you boot it into recovery? Your bat may be dead from extensively flashing stuff, so plug the phone to the power cable and press and hold VolDown+Power for some good 30s, then you can conclude your phone wont boot into recovery and maybe need an unbrick.
aredpanda said:
Can you boot it into recovery? Your bat may be dead from extensively flashing stuff, so plug the phone to the power cable and press and hold VolDown+Power for some good 30s, then you can conclude your phone wont boot into recovery and maybe need an unbrick.
Click to expand...
Click to collapse
Yeah, it didn't boot into recovery
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
aredpanda said:
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
Click to expand...
Click to collapse
No, it doesn't
aredpanda said:
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
Click to expand...
Click to collapse
I turned off the signature check, W8
If your led doesnt light when your phone is plugged to the wall, this is behind the hard unbricking procedure and your phone is indeed, dead.
Sent from my ONE E1003 using Tapatalk
This issue has been resolved via PM,
Can a mod please close this thread?
No idea what it could be besides corrupt firmware which I've never heard of happening before. The Qualcomm utility should work just fine. Leave it plugged in for an hour or two and see if anything happens
Did you install the qualcomm drivers? If not do it again carefully with driver enforcement off. It works like a charm. Have bricked my device twice as of now and it worked.
Long story short....in my efforts to flash the 10B TOT file, the flash tool got to 94% and started the phone reboot step, but the phone never rebooted thus the flash was a failure. When I tried to re-do the steps to flash the 10B TOT, I found out that I was no longer able to get into download mode. In my computer's device settings, when the phone is connected with a USB it now shows up as Qualcomm HS-USBQloader 9008. I looked up the threads about this problem and started the process of getting this fixed using the BoardDiag tool, but that process fails at the part where I attempt to run the AP and EMMC tests (gives me a message saying "Device was not found in DLOAD trying to install flasher). I have not found any practical fix for this error.
Am I completely screwed now, or is there a step somewhere I'm missing? I've been at this for 5 hours.
ChiefIlliniwek5 said:
Long story short....in my efforts to flash the 10B TOT file, the flash tool got to 94% and started the phone reboot step, but the phone never rebooted thus the flash was a failure. When I tried to re-do the steps to flash the 10B TOT, I found out that I was no longer able to get into download mode. In my computer's device settings, when the phone is connected with a USB it now shows up as Qualcomm HS-USBQloader 9008. I looked up the threads about this problem and started the process of getting this fixed using the BoardDiag tool, but that process fails at the part where I attempt to run the AP and EMMC tests (gives me a message saying "Device was not found in DLOAD trying to install flasher). I have not found any practical fix for this error.
Am I completely screwed now, or is there a step somewhere I'm missing? I've been at this for 5 hours.
Click to expand...
Click to collapse
Have you installed the correct drivers for the Qualcomm HS-USBQloader for your version of windows?
Look at this guide it works perfectly. http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
netookska05 said:
Have you installed the correct drivers for the Qualcomm HS-USBQloader for your version of windows?
Look at this guide it works perfectly. http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
Click to expand...
Click to collapse
Just to make sure I was doing everything right, I installed the Qualcomm drivers with the test mode on for driver signing. My phone, when plugged into the computer, still shows up as Qualcomm HS-USB QDLoader 9008. So it's my understanding that I don't need to do the steps which detail how I would need to break into my phone and use wires and solder. Based on everything I've read, I should be able to use the BoardDiag tool, but it keeps telling me in one fashion or another that it can't connect to the phone. Sometimes it will tell me "Check PMIC first and if still boot problem, replace AP", other times it will give me the same message I was getting originally saying "Device was not found in DLOAD trying to flash programmer".
ChiefIlliniwek5 said:
Just to make sure I was doing everything right, I installed the Qualcomm drivers with the test mode on for driver signing. My phone, when plugged into the computer, still shows up as Qualcomm HS-USB QDLoader 9008. So it's my understanding that I don't need to do the steps which detail how I would need to break into my phone and use wires and solder. Based on everything I've read, I should be able to use the BoardDiag tool, but it keeps telling me in one fashion or another that it can't connect to the phone. Sometimes it will tell me "Check PMIC first and if still boot problem, replace AP", other times it will give me the same message I was getting originally saying "Device was not found in DLOAD trying to flash programmer".
Click to expand...
Click to collapse
Have you tried to boot into DL mode remove battery reinsert battery and press vol up while connecting to computer. If you are able to get into that mode you can downgrade to the vs98510b.tot. Can you post a computer screen shot of your setup of your Boarddiag?
netookska05 said:
Have you tried to boot into DL mode remove battery reinsert battery and press vol up while connecting to computer. If you are able to get into that mode you can downgrade to the vs98510b.tot. Can you post a computer screen shot of your setup of your Boarddiag?
Click to expand...
Click to collapse
It won't let me boot into download mode.
I've attached a screenshot of what my BoardDiag screen looks like. I extracted the TOT files that the tool created to my bare C: drive because any time I tried to change the directory for the location of those files it would cause the program to crash.
ChiefIlliniwek5 said:
It won't let me boot into download mode.
I've attached a screenshot of what my BoardDiag screen looks like. I extracted the TOT files that the tool created to my bare C: drive because any time I tried to change the directory for the location of those files it would cause the program to crash.
Click to expand...
Click to collapse
Ok so when you plug in your phone to the computer does it say installing the qualcomm driver or does it just show up as the qualcomm in device manager. I had that when I bricked my phone and had to redo the wire trick. Once I did it the installing qualcomm drivers notice came up and I was able to run the boarddiag with not problem. If all else fails give the wire trick a try. Here's another similar guide that will help too. I turned off driver signing on computer bootup just for reference. http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
netookska05 said:
Ok so when you plug in your phone to the computer does it say installing the qualcomm driver or does it just show up as the qualcomm in device manager. I had that when I bricked my phone and had to redo the wire trick. Once I did it the installing qualcomm drivers notice came up and I was able to run the boarddiag with not problem. If all else fails give the wire trick a try. Here's another similar guide that will help too. I turned off driver signing on computer bootup just for reference. http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Click to expand...
Click to collapse
The first time I plugged it in after installing the Qualcomm drivers the window popped up to show that the device drivers were being installed and it completed successfully.
I'm trying to reach out to tungkick since I've seen in other threads that he has helped people who have run into the same issues I'm having. I'm hoping he can fix it without me having to crack open my phone.
ChiefIlliniwek5 said:
The first time I plugged it in after installing the Qualcomm drivers the window popped up to show that the device drivers were being installed and it completed successfully.
I'm trying to reach out to tungkick since I've seen in other threads that he has helped people who have run into the same issues I'm having. I'm hoping he can fix it without me having to crack open my phone.
Click to expand...
Click to collapse
Does your comm port in qualcomm driver in device settings and boarddiag comm port match?
Also, were you already rooted and wanted to go back to stock or what version of software were you downgrading from ( ex. 46A,47A what).
netookska05 said:
Does your comm port in qualcomm driver in device settings and boarddiag comm port match?
Click to expand...
Click to collapse
Yes it does. As far as I can tell I'm doing everything right based on the tutorials that are out there.
ChiefIlliniwek5 said:
Yes it does. As far as I can tell I'm doing everything right based on the tutorials that are out there.
Click to expand...
Click to collapse
What software are you coming from? That was the second part of my response. Take a look at this if you haven't already. http://forum.xda-developers.com/lg-...lcomm-9008-t3072091/post59881075#post59881075
netookska05 said:
What software are you coming from? That was the second part of my response. Take a look at this if you haven't already. http://forum.xda-developers.com/lg-...lcomm-9008-t3072091/post59881075#post59881075
Click to expand...
Click to collapse
So the long story is that I was originally running 47A stock with root and TWRP recovery. I was having TERRIBLE battery life and it got to the point where I couldn't take it any more so I decided to flash a CM13 nightly. I was going to test the waters to see if I could use a systemless SuperSU version with CM13 so when I flashed CM13 I also flashed SuperSU 2.68 at the same time. It turns out that's a big no-no. So when I tried to reboot, I got the error message that the secure boot failed, or something to that effect. So after looking at posts on XDA I intended on doing the "revert to 10B from 47A" method with a TOT file and the flash tool. Everything with that was working great...it got to 94% complete and got the point in the process where the phone reboots, but when the phone left download mode it never came back and the flash tool never made a re-connection with the phone to complete the end of the process. From that point on, I could not even load into download mode, thus here I am.
netookska05 said:
What software are you coming from? That was the second part of my response. Take a look at this if you haven't already. http://forum.xda-developers.com/lg-...lcomm-9008-t3072091/post59881075#post59881075
Click to expand...
Click to collapse
Ok so I used the androidbrick tool in that link you sent me and the process seems to have gone through correctly. After re-installing my battery the phone booted to the LG screen, then showed the little android guy with a progress bar, but that screen didn''t last long before the phone rebooted again and this time after the LG screen I got a screen that said "miniOS" and following that came a blue screen with the words "Factory Reset Status" and a big red number 2. So that's where I'm at now and I'm going to look up info on that to see what I do next. If you have any experience with this step please let me know.
Boot into download mode Volume up and us lg flash tool and tot again. It should say 3 when successful.
netookska05 said:
Boot into download mode Volume up and us lg flash tool and tot again. It should say 3 when successful.
Click to expand...
Click to collapse
Ok, this is where I was earlier today and when it got to about 94% complete and commanded the phone to reboot, the phone never came back to a state that allowed the flash tool to complete. I've seen some sites talk about having to hold the up volume button at a certain juncture around the time that it failed for me last time. Is there some trick to this?
netookska05 said:
Boot into download mode Volume up and us lg flash tool and tot again. It should say 3 when successful.
Click to expand...
Click to collapse
It did it again! Phone got to 100% on the flash and the tool got to the restart command, but the phone never came back on after leaving the download mode from the reboot command. I even was holding the volume up like another website said when the reboot occurred. I also changed the setting from "Upload DL" to "Board DL" as suggested by others in various threads. The error I'm getting after the tool says it failed is "USB port open FAIL!"
ChiefIlliniwek5 said:
It did it again! Phone got to 100% on the flash and the tool got to the restart command, but the phone never came back on after leaving the download mode from the reboot command. I even was holding the volume up like another website said when the reboot occurred. I also changed the setting from "Upload DL" to "Board DL" as suggested by others in various threads. The error I'm getting after the tool says it failed is "USB port open FAIL!"
Click to expand...
Click to collapse
Ok, we are back up and running! I went through all the steps again going all the way back to the androidbrick tool. This time when the phone boot into miniOS mode and was still on that animation, I hit the power button (something I saw on another post) and it took me to the AAT screen. I had seen a thread about this somewhere and followed those steps to have the phone reboot into the setup wizard and we are all good now! WHEW! The only thing that sucks is throughout this whole process I've lost well over 100 photos of my son . Oh well....I saved myself a few hundred bucks. Thanks for all of your help!!
ChiefIlliniwek5 said:
Ok, we are back up and running! I went through all the steps again going all the way back to the androidbrick tool. This time when the phone boot into miniOS mode and was still on that animation, I hit the power button (something I saw on another post) and it took me to the AAT screen. I had seen a thread about this somewhere and followed those steps to have the phone reboot into the setup wizard and we are all good now! WHEW! The only thing that sucks is throughout this whole process I've lost well over 100 photos of my son . Oh well....I saved myself a few hundred bucks. Thanks for all of your help!!
Click to expand...
Click to collapse
You sure did save and no problem glad to help. Always store photos on ext sd. Enjoy
netookska05 said:
You sure did save and no problem glad to help. Always store photos on ext sd. Enjoy
Click to expand...
Click to collapse
ChiefIlliniwek5 said:
Ok, we are back up and running! I went through all the steps again going all the way back to the androidbrick tool. This time when the phone boot into miniOS mode and was still on that animation, I hit the power button (something I saw on another post) and it took me to the AAT screen. I had seen a thread about this somewhere and followed those steps to have the phone reboot into the setup wizard and we are all good now! WHEW! The only thing that sucks is throughout this whole process I've lost well over 100 photos of my son . Oh well....I saved myself a few hundred bucks. Thanks for all of your help!!
Click to expand...
Click to collapse
I also wanted to add, I use the Mega cloud service app with 50 GB free. I have it configured to automatically back up my pictures and videos whenever I'm connected to WiFi. I save photos and videos to internal storage because it's faster and more reliable than Micro SD cards are.
roirraW "edor" ehT said:
I also wanted to add, I use the Mega cloud service app with 50 GB free. I have it configured to automatically back up my pictures and videos whenever I'm connected to WiFi. I save photos and videos to internal storage because it's faster and more reliable than Micro SD cards are.
Click to expand...
Click to collapse
@roirraW "edor" ehT Good idea I may just do that myself.
hey guys new to this place, not that new, i've always search this forum for some rom or how to fix stuff and other help but never post anything here.
so lets get straight to the point. so basically i want to revive my old samsung galaxy tab 10.1. you know, for fun and nostalgia haha (if possible). so i don't really remember what i did to this tablet that it becomes like what it is today. cannot be turned on, no display when charging, no nothing. i do remember rooting it before. when it charge, there is a little warm going on on the tablet but nothing happen. when i connect it to my pc, it recognize it as unknown device the first time, and then i hold the power button for couple of second and my pc recognize it again but now as apx but no driver available. so i made a little research just now and i found that the tablet may have a chance to be fix with the use of nvflash or something. so all im saying is it really my tab can be fix without spending money? if can how do i do it? i have a little experience about flashing rom and recovery. but nothing on how to use nvflash. i do really appreciate your help to bring me back this tab that meant so much for me and my family back in the days.
http://www.gsmforum.ru/threads/223383-Samsung-GT-P7500-%D0%BE%D0%BF%D1%80%D0%B5%D0%B4%D0%B5%D0%BB%D1%8F%D0%B5%D1%82%D1%81%D1%8F-%D0%BA%D0%B0%D0%BA-APX
you download this files...let me know if you fix your tab
so its seems that i need to register for to download 3 files right? now im waiting for the email confirmation which take too long
yes, i can't upload this files...there's a error! did you downloaded 3 files and runned the process? the user doesn't write after the process but i think problem fixed. Ask you with topic when you registe youself...
jackfiq said:
so its seems that i need to register for to download 3 files right? now im waiting for the email confirmation which take too long
Click to expand...
Click to collapse
i can upload only 1 file of 3 files.... 2 files're > of 20MB...let me know if you fix your tab
bollicine said:
i can upload only 1 file of 3 files.... 2 files're > of 20MB...let me know if you fix your tab
Click to expand...
Click to collapse
can you guide me on how to do it? from start till end. thank you soo much for helping me out
jackfiq said:
can you guide me on how to do it? from start till end. thank you soo much for helping me out
Click to expand...
Click to collapse
1) to install apx driver (NVIDIA driver )
2) to run file .batch
i think this! you check now and write the result!
https://forum.xda-developers.com/showthread.php?t=1130574]
bollicine said:
1) to install apx driver (NVIDIA driver )
2) to run file .batch
i think this! you check now and write the result!
Click to expand...
Click to collapse
hey i got a problem, my pc doesnt detect my device as apx something, instead it detects as unknown usb device (invalid device descriptor) . (i've also reset my pc months ago ).
jackfiq said:
hey i got a problem, my pc doesnt detect my device as apx something, instead it detects as unknown usb device (invalid device descriptor) . (i've also reset my pc months ago ).
Click to expand...
Click to collapse
you install the driver for to use nvflash...read this guide to install the driver https://forum.xda-developers.com/showthread.php?t=1130574]
but to use file.batch 1th recovery_P75xx.bat of Recovery_P75xx_110710_RemoveUsbDriver.zip to run the nvflash and the recovery and you post the result. bye
I think your battery is complet down, that means the current is under the charging level.
bierma32 said:
I think your battery is complet down, that means the current is under the charging level.
Click to expand...
Click to collapse
Ooo okok ill try to charge it first then but right now im study away from my home so its gonna take a while but thank you soo much for helping me put
jackfiq said:
Ooo okok ill try to charge it first then but right now im study away from my home so its gonna take a while but thank you soo much for helping me put
Click to expand...
Click to collapse
Ok! you connect it with power supply for a night.... i hope you can to recharge it if you don't see the battery icon...otherwise you try with a usb cable cut directly on battery's connector and recharge it...you've to remove back cover. Update us, bye!
bollicine said:
Ok! you connect it with power supply for a night.... i hope you can to recharge it if you don't see the battery icon...otherwise you try with a usb cable cut directly on battery's connector and recharge it...you've to remove back cover. Update us, bye!
Click to expand...
Click to collapse
hello again. sorry for didnt post any update . im actually really busy with studies and i already told that my university is far from my home. so i didnt get a chance to get back here until a month. now im here exicted to the thing only then come out with this type of output
Recovery the bootloader...
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
so i've made a little research.. so it seems that my device's bootloader is locked. so is there anyway to unlock my bootloader??
by the way im really sorry i didnt update for a long time. but i hope you still want to keep in touch with me to solve my problem. much thanks!