Related
Hi Everyone
I have a Telstra HTC One XL which is unlocked, rooted and running Viper 3.2.7 - it has been working perfectly for a year.
On Friday it reported that the SD card was mounted read only - I did some forum searches and have tried mounting & scanning the SD card which didn't resolve anything. I have a backup of my data so thought that I'd wipe the device and upgrade to the latest ROM (v4.2.0)
However, the device is in permanent read only mode. I can (via Windows) apparently copy the ROM zip file to the device but it is never really there - disconnect the phone and re-connect and it's as if the copy had never happened.
I can also delete files but, after disconnecting and reconnecting, they're magically back
Deleting files via TWRP doesn't work either (same result)
Re-installing the old ROM (still on the SD card) doesn't happen either - the install says complete but even having told it to not keep my settings/data/programs everything is still there
I've tried sideloading the ROM update (says complete but actually isn't)
Wiping the system, caches etc via TWRP again reports as successful but isn't
I can't update TWRP, although it says OKAY
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.0-evita.img
sending 'recovery' (8176 KB)...
OKAY [ 1.030s]
writing 'recovery'...
OKAY [ 3.323s]
finished. total time: 4.368s
I can't manually update the boot.img, although again it says OKAY
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
sending 'boot' (6054 KB)...
OKAY [ 0.889s]
writing 'boot'...
OKAY [ 2.168s]
finished. total time: 3.073s
I've tried a couple of versions of fastboot as well.
Given that there's nothing I want on the phone and it's just not working correctly, I'm happy to do/try anything at all but have now run out of ideas - does anyone have any thoughts for me?
Many thanks in advance
David
Ive about lost my mind trying to restore my nexus 5 to stock .Img . I have tried Wugfresh toolkit v1.8.2 i have adb installed i have google drivers installed.. I have tried to manually flash everything via cmd prompt. I have checked in device manager to make sure everything looks good
I am assumingmy device is being recognized based on that fact it is stating these errors ....I keep getting boot sig error and out of memory error.
I have rebooted into twrp done a data wipe factory reset wipe tried it all as mentioned to try in some topics ive read... I cant find any fix or any relevant topic in regards to these errors on a google search people just say try this and that..
When i try to run the toolkit again same errors.
This is more difficult than even htc ever was for me.
Any help anyone have any ideas?
Could you post a screen shot or a log of what is printed out?
heres what the toolkit says after errors
sending 'bootloader' (2508 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.099s
rebooting into bootloader...
FAILED (unknown status code)
finished. total time: 1.052s
sending 'radio' (42049 KB)...
FAILED (command write failed (Invalid argument)
finished. total time: -0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
archive does not contain 'boot.sig'
error: out of memory
Try a different usb port. Make sure it's a usb 2.0. If that doesn't work, try another usb cable.
Errors such as: "out of memory" - "too many links" - "data transfer failure" are usually USB problems.
heres what the toolkit says after errors
sending 'bootloader' (2508 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.099s
rebooting into bootloader...
FAILED (unknown status code)
finished. total time: 1.052s
sending 'radio' (42049 KB)...
FAILED (command write failed (Invalid argument)
finished. total time: -0.000s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
archive does not contain 'boot.sig'
error: out of memory
I have tried other usb ports.. and cords..
I have tried my other USB port I'm on windows 8 gateway PC.
It recognizes USB debugging and all that cause the script reboots my phone into bootloader
Cf auto root worked fine for me yesterday and that was in the bootloader mode I could swear I have the correct connections and drivers ... It seems like its something else ... Why would I get a out of memory error and no Boot SIG..
I googled that error and others have mentioned it but Never mentioned what caused it .
lojak29 said:
I have tried my other USB port I'm on windows 8 gateway PC.
It recognizes USB debugging and all that cause the script reboots my phone into bootloader
Cf auto root worked fine for me yesterday and that was in the bootloader mode I could swear I have the correct connections and drivers ... It seems like its something else ... Why would I get a out of memory error and no Boot SIG..
I googled that error and others have mentioned it but Never mentioned what caused it .
Click to expand...
Click to collapse
what happens when you do this way?http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Yet another reason not to use toolkits. Since you're using toolkits (for all intents and purposes CF Auto Root is a toolkit), you obviously don't have the SDK installed and the error messages indicate that the USB drivers aren't properly installed. You can't trust toolkits to properly install the USB drivers, and without the drivers the toolkit is worthless, you can't do anything.
Do it the right way, and make sure you install the drivers through the SDK manager, not through plug and play... [GUIDE] Nexus 5 - How to Unlock Bootloader, Install Custom Recovery and Root
Download USB drivers.
Extract the drivers.
Connect phone in fastboot mode.
Open device manager.
In "Android Device" topic right click on "Android Bootloader Interface" and select "Update Driver software..." (depending on what drivers are already installed on your pc this "Android Bootloader Interface" could be "Samsung Galaxy Bootloader Interface" or something similar.)
Install the new drivers.
Download adb+fastboot.
Extract it, and place the adb folder to an obvious place, like C:\ or C:\Users\<Your user name>
Open Control Panel.
If the view settings is set to "Cathegories" then click on "System and Security" then select "System".
If the view settigns is set to anything but "Cathegories" then just click on "System".
In "System" window select "Advanced system settings".
Select "Environment Varaibles..." in "System Proerties" window.
At "System variables" section in the "Environment Variables" window look for "Path".
Select it then click on "Edit...".
Place a semicolon (this ===> ; <=== this) at the end of the "Variable value:" line in the "Edit System Varaible" window.
Right after the semicolon type the path to the adb folder. If you placed your adb folder to C:\ then it should look like something like this: ...blablablabla;C:\adb
Then click on "OK" in every window.
Download stock firmware from google.
Extract it (you may need winrar).
Connect phone in fastboot mode.
Double click on flash-all.bat in the previously extracted folder.
Andere dont forget to disable driver signature authentication in Win 8/8.1.
Sent from my Nexus 10 using xda app-developers app
gee2012 said:
Andere dont forget to disable driver signature authentication in Win 8/8.1.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Don't need to do that (or I didn't anyway)
EddyOS said:
Don't need to do that (or I didn't anyway)
Click to expand...
Click to collapse
My USB driver didn't installatll at first before i did that ? ?
Verstuurd vanaf mijn Nexus 5 met Tapatalk
gee2012 said:
My USB driver didn't installatll at first before i did that ? ?
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Click to expand...
Click to collapse
So long as you have the latest drivers from the SDK you should be fine
EddyOS said:
So long as you have the latest drivers from the SDK you should be fine
Click to expand...
Click to collapse
I always use the Google USB drivers and never had an issue.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
gee2012 said:
I always use the Google USB drivers and never had an issue.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Click to expand...
Click to collapse
Strange, it's always worked fine on my Windows 8.1 laptop - even with USB3
Tried to flash stock firmware with fastboot. It didnt seemed to finish, so i tried rebooting. But now it wont boot. Just vibrates but when i plug in the usb cable, windows tries to install a driver for it. In device manager it says "APX"
Motawa88 said:
Tried to flash stock firmware with fastboot. It didnt seemed to finish, so i tried rebooting. But now it wont boot. Just vibrates but when i plug in the usb cable, windows tries to install a driver for it. In device manager it says "APX"
Click to expand...
Click to collapse
Do you have nvflash backups? If not you've killed it interrupting a low level nand flash.... I don't know what you were expecting to happen?
If you only have APX I'm sorry to say there are only 2 ways to recover.
1. NVFLash restore
2. New mother board
sbdags said:
Do you have nvflash backups? If not you've killed it interrupting a low level nand flash.... I don't know what you were expecting to happen?
If you only have APX I'm sorry to say there are only 2 ways to recover.
1. NVFLash restore
2. New mother board
Click to expand...
Click to collapse
I dont know. This is like my 70th android device and this is the first time i messed something up while flashing
I just bought the tablet so i do have a 60 days refund in my country. will asus still see if the bootloader is unlocked?
Motawa88 said:
I dont know. This is like my 70th android device and this is the first time i messed something up while flashing
I just bought the tablet so i do have a 60 days refund in my country. will asus still see if the bootloader is unlocked?
Click to expand...
Click to collapse
They'll know you unlocked it as you had to use their unlock tool which dialled home and got the unlock keys....... so yes it is in their database so you warranty is now void I'm afraid.
Asus TF700T Tablet fix
Motawa88 said:
Tried to flash stock firmware with fastboot. It didnt seemed to finish, so i tried rebooting. But now it wont boot. Just vibrates but when i plug in the usb cable, windows tries to install a driver for it. In device manager it says "APX"
Click to expand...
Click to collapse
I had similar issues and spent many a day trying to fix my TF700, almost resigned to the fact that the motherboard was stuffed, but then came across a method that I hadn't tried and now I am back up and running with a stock Rom. Here is the record of what I did, maybe it will help:
Asus TF700T Tablet fix - And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames. YOU DO THIS AT YOUR OWN RISK
Ok, so I think that I may have lost power during an upgrade (can’t think of any other reason for it!!) and ended up soft bricking my Asus TF700T tablet and recovery attempts would just lead to the dead Android with a red triangle with an exclamation point in the middle. My warranty having expired with Asus and any attempt for their assistance proved fruitless.
Well I researched and tried absolutely everything out there – (Hard Reset, installing TWRP, used a tool called Motochopper and flashing a custom ROM, downloaded and renaming .zip files, putting it onto a Micro SDcard is formatted Fat32, Scotts Tf700t Recovery etc.etc. etc.)
I even took it to the local shops and paid to have one of the Mobile Technician pop-up stores take a look at it, then a friendly techno geek………all with the same suggestions most likely a motherboard/hard drive problem.
My Asus TF700T tablet eventually ended up with just the plain white ASUS logo in the middle of the screen, some small print in the top left corner followed by the dreaded words “Unrecoverable Bootloader Error (0x00000000)”.
During all of my research I was led to believe that if you can still get to the recovery screen, where you see the 4 icons, all is not lost so I persisted.
Here is the instructions that I followed that restored my TF700T:
Download and install ADB, Fastboot and the required drivers - Download and run this cool little tool which has it all packed into one: [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
NOTE: at the moment Fastboot seems to have issues with Windows 8
This awesome tool installs the ADB and Fastboot.exe to a folder on your C:\ drive (look for a file titled “adb”) as well as the corresponding drivers. This takes about 15 seconds to install following the prompts.
I installed the device drivers - if you have already tried to connect the tablet to your PC and it's recognised as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it.
Download the latest firmware from Asus (Always make sure that you download the correct SKU version -WW, US etc.) and extract the zip twice so you access the blob file (a blob is a collection of binary data stored as a single entity) – copy and paste this blob file into the previously mentioned “adb” folder on your C:\ drive.
Reset the device with a paperclip/needle (about 2 cm down of the SDcard slot)
Power down the tablet and disconnect it from the keyboard dock.
Connect it to your computer via the original USB cable.
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in Fastboot mode and you will see three or 4 icons (depending on the bootloader version). Select the USB icon to get into the Fastboot mode.
Your PC should acknowledge that a USB device has been connected (an audible indication) Don’t panic if the device does not appear under “My Computer” (as mine did not either – Fastboot will still communicate with it), you can go into Control Panel/Hardware and Sound/ Device Manager and you may see “Fastboot” icon, expand this and the device will be represented again by the “Fastboot” icon. Right click, select “Properties”, Driver tab and then select “Update Driver” and allow it to search automatically and update from the internet. This should then update and change to Asus icons. You now can be certain that you have the current device drivers.
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7 press Shift + right click and select "Open command window here".
In the resulting command prompt screen type the following codes (those in bold):
C:\adb\ (or whatever the path to your fastboot folder is..)
fastboot devices (If that command returns a string of numbers and letters, you are good as gold. If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot)
Followed by each in turn of the below, selecting Yes as required and allowing each to complete the process:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
The resulting screen should look something like this below – NOTE, I did make a couple of typos while I was attempting this which returned some multiple choice garble if this happens recheck you input instructions:
E:\asus>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.979s]
finished. total time: 1.980s
E:\asus>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.023s]
finished. total time: 1.025s
E:\asus>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 39.623s]
finished. total time: 39.624s
E:\asus>fastboot erase boot
erasing 'boot'...
OKAY [ 0.303s]
finished. total time: 0.304s
E:\asus>fastboot erase misc
erasing 'misc'...
OKAY [ 0.602s]
finished. total time: 0.603s
E:\asus>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.459s]
finished. total time: 1.460s
fastboot -i 0x0B05 flash system c:\adb\TF700T\blob - depending where you stored your blob, also this was the first time that I saw the loading bar appear on my tablet.
It will now go through the process of reinstalling your Android stock ROM and you should see the something similar to the following:
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.731s]
sending 'system' (800935 KB)...
OKAY [134.276s]
writing 'system'...
OKAY [131.640s]
finished. total time: 267.649s
fastboot -i 0x0B05 reboot
E:\asus>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
E:\asus>
I disconnected and rebooted My Asus TF700T and I now have a fully functioning Tablet with a stock ROM.
It has been reported that after completing this you may have some issues getting back get into recovery, hitting RCK and getting the dreaded dead Android (with a red triangle with an exclamation point in the middle). I have not attempted this but have been led to believe that flashing TWRP 2.7.0.1 via Fastboot works.
All acknowledgement and appreciation for this method should go to Buster99, a Senior Member of XDA Developers
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
And to Snoop05, also a Senior Member of XDA Developers for the awesome ADB/Fastboot/Driver tool.
http://forum.xda- developers.com/showthread.php?t=2588979
To whom I am most grateful for the return of my tablet to a working state, I hope this works for you. Good Luck.
A big big thanks. This instructions worked for my Asus tf700t. It was hard bricked.
Browndog181 said:
I had similar issues and spent many a day trying to fix my TF700, almost resigned to the fact that the motherboard was stuffed, but then came across a method that I hadn't tried and now I am back up and running with a stock Rom. Here is the record of what I did, maybe it will help:
Asus TF700T Tablet fix - And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames. YOU DO THIS AT YOUR OWN RISK
Ok, so I think that I may have lost power during an upgrade (can’t think of any other reason for it!!) and ended up soft bricking my Asus TF700T tablet and recovery attempts would just lead to the dead Android with a red triangle with an exclamation point in the middle. My warranty having expired with Asus and any attempt for their assistance proved fruitless.
Well I researched and tried absolutely everything out there – (Hard Reset, installing TWRP, used a tool called Motochopper and flashing a custom ROM, downloaded and renaming .zip files, putting it onto a Micro SDcard is formatted Fat32, Scotts Tf700t Recovery etc.etc. etc.)
I even took it to the local shops and paid to have one of the Mobile Technician pop-up stores take a look at it, then a friendly techno geek………all with the same suggestions most likely a motherboard/hard drive problem.
My Asus TF700T tablet eventually ended up with just the plain white ASUS logo in the middle of the screen, some small print in the top left corner followed by the dreaded words “Unrecoverable Bootloader Error (0x00000000)”.
During all of my research I was led to believe that if you can still get to the recovery screen, where you see the 4 icons, all is not lost so I persisted.
Here is the instructions that I followed that restored my TF700T:
Download and install ADB, Fastboot and the required drivers - Download and run this cool little tool which has it all packed into one: [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
NOTE: at the moment Fastboot seems to have issues with Windows 8
This awesome tool installs the ADB and Fastboot.exe to a folder on your C:\ drive (look for a file titled “adb”) as well as the corresponding drivers. This takes about 15 seconds to install following the prompts.
I installed the device drivers - if you have already tried to connect the tablet to your PC and it's recognised as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it.
Download the latest firmware from Asus (Always make sure that you download the correct SKU version -WW, US etc.) and extract the zip twice so you access the blob file (a blob is a collection of binary data stored as a single entity) – copy and paste this blob file into the previously mentioned “adb” folder on your C:\ drive.
Reset the device with a paperclip/needle (about 2 cm down of the SDcard slot)
Power down the tablet and disconnect it from the keyboard dock.
Connect it to your computer via the original USB cable.
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in Fastboot mode and you will see three or 4 icons (depending on the bootloader version). Select the USB icon to get into the Fastboot mode.
Your PC should acknowledge that a USB device has been connected (an audible indication) Don’t panic if the device does not appear under “My Computer” (as mine did not either – Fastboot will still communicate with it), you can go into Control Panel/Hardware and Sound/ Device Manager and you may see “Fastboot” icon, expand this and the device will be represented again by the “Fastboot” icon. Right click, select “Properties”, Driver tab and then select “Update Driver” and allow it to search automatically and update from the internet. This should then update and change to Asus icons. You now can be certain that you have the current device drivers.
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7 press Shift + right click and select "Open command window here".
In the resulting command prompt screen type the following codes (those in bold):
C:\adb\ (or whatever the path to your fastboot folder is..)
fastboot devices (If that command returns a string of numbers and letters, you are good as gold. If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot)
Followed by each in turn of the below, selecting Yes as required and allowing each to complete the process:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
The resulting screen should look something like this below – NOTE, I did make a couple of typos while I was attempting this which returned some multiple choice garble if this happens recheck you input instructions:
E:\asus>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.979s]
finished. total time: 1.980s
E:\asus>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.023s]
finished. total time: 1.025s
E:\asus>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 39.623s]
finished. total time: 39.624s
E:\asus>fastboot erase boot
erasing 'boot'...
OKAY [ 0.303s]
finished. total time: 0.304s
E:\asus>fastboot erase misc
erasing 'misc'...
OKAY [ 0.602s]
finished. total time: 0.603s
E:\asus>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.459s]
finished. total time: 1.460s
fastboot -i 0x0B05 flash system c:\adb\TF700T\blob - depending where you stored your blob, also this was the first time that I saw the loading bar appear on my tablet.
It will now go through the process of reinstalling your Android stock ROM and you should see the something similar to the following:
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.731s]
sending 'system' (800935 KB)...
OKAY [134.276s]
writing 'system'...
OKAY [131.640s]
finished. total time: 267.649s
fastboot -i 0x0B05 reboot
E:\asus>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
E:\asus>
I disconnected and rebooted My Asus TF700T and I now have a fully functioning Tablet with a stock ROM.
It has been reported that after completing this you may have some issues getting back get into recovery, hitting RCK and getting the dreaded dead Android (with a red triangle with an exclamation point in the middle). I have not attempted this but have been led to believe that flashing TWRP 2.7.0.1 via Fastboot works.
All acknowledgement and appreciation for this method should go to Buster99, a Senior Member of XDA Developers
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
And to Snoop05, also a Senior Member of XDA Developers for the awesome ADB/Fastboot/Driver tool.
http://forum.xda- developers.com/showthread.php?t=2588979
To whom I am most grateful for the return of my tablet to a working state, I hope this works for you. Good Luck.
Click to expand...
Click to collapse
I am trying to fix my tf700. Trying to flash the blob..
Code:
D:\Desktop\TF700>fastboot -i 0x0B05 flash system d:\desktop\TF700\blob
erasing 'system'...
OKAY [ 0.702s]
sending 'system' (800927 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3.439s
Any idea?
Yeah. I Put the blob into your fastboot directory. Open cmd from there and flash it with fastboot - i 0x0b05 flash system blob
berndblb said:
Yeah. I Put the blob into your fastboot directory. Open cmd from there and flash it with fastboot - i 0x0b05 flash system blob
Click to expand...
Click to collapse
Same result. Fixed it by flashing a bootloader blob first.
Fastboot flash staging bootloader-blob
krugm0f0 said:
Same result. Fixed it by flashing a bootloader blob first.
Fastboot flash staging bootloader-blob
Click to expand...
Click to collapse
Are you up and running now?
You may want to try a different USB port. I had the same error when I tried to use a USB hub to connect to my CPU.
TWRP recovery for Nabi Bigtab 20"
Must have unlocked bootloader
Download:attachment below
install via adb
"adb reboot-bootloader"
"fastboot flash recovery recovery.img"
Compiled by me with help from @aicjofs
I need help getting a fastboot driver to work for this tablet. So far I've had no luck. What drivers did you use?
Just in case others have this problem and arrive here....
I recently got a Nabi Big 20 HD tablet to use as a camera viewer in a nursery at our church. The only problem was, when I turned it on, it kept giving me an error, stating that I had to hook up to the wifi, and that the FUHU servers had a problem. Essentially, since Fuhu went out of business, you can’t connect to the fuhu servers.
Since you can’t connect to the servers, setup can’t be completed, and this 20″ tablet became a 20″ paperweight. Obviously, that would not do, so I figured out how to use fastboot mode, TWRP, and the advanced file manager to delete the unneeded junk to make the tablet functional again. Below are my instructions, performed from a Linux computer. You could do this from Windows as well, if you download the right tools.
Before you begin, you will need the TWRP recovery image, which you can get from here: http://www.mediafire.com/folder/rul6liygr1rw3/Nabi_big_20_hd_tablet or from https://forum.xda-developers.com/android/development/recovery-nabi-bigtab-hd-20-t3035372
Power off the tablet.
Hold the volume up and power on buttons, and release them when you see the menu options.
NOTE: This is actually fastboot mode!
Perform an OEM unlock
[email protected]:~$ fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 13.625s]
finished. total time: 13.625s
[email protected]:~$
After this it reboots and starts up again, so power off the tablet.
Hold the volume up and power on buttons again, release them when you see the menu options.
NOTE: Once again, this is actually fastboot mode!
Flash the recovery image.
[email protected]:~/Downloads$ fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (8646 KB)...
OKAY [ 0.313s]
writing 'recovery'...
OKAY [ 0.314s]
finished. total time: 0.627s
[email protected]:~/Downloads$
From the still open menu, use the volume keys to scroll down to “recovery mode” and press the power button once to choose it. NOTE: it will show the NABI screen, then reboot into TWRP. Unfortunately, ADB does not work in this version of TWRP.
Go to “Mount” and check “System” and then click to disable MTP.
Press the home key or back key to get back to the main menu.
Click “Advanced”.
Click “file manager”.
Scroll to “priv-app” and select it.
Click on each of these items and choose to delete them:
fuhu_addapps2.apk
fuhu_appzone2.apk
fuhu_drmmanagerservice.apk
fuhu_nabiaccountmanager.apk
fuhu_nabiupdater.apk
–Personally, I just deleted all “fuhu” apps in this folder, but I think you only need those ones.
Then in the “app” folder, delete all the fuhu apps. Yes, I’m pretty sure you need to delete all of these ones.
Select the home or back button to get to the main TWRP screen.
Reboot to system.
Enjoy!
NOTE: It should start up, and may go through the Google setup (if you never started it before), and then will drop you off in “parent mode”.
At this point, I recommend installing a regular launcher, such as Trebuchet, Apex launcher, Nova launcher, etc. I used Apex launcher personally, because you can “hide” unwanted apps, and I use it to hide the unwanted Nabi apps. You should be able to see the Chrome browser in the parent mode window, use that to download the apk for the launcher you want (or use the Google account if you set up an account).
Once a launcher is installed, press the home key, and choose to always use the launcher you installed. You can now use this tablet as a regular Android tablet.
TWRP does have the option to install SuperSU and root the device. That’s completely up to you. Kingo Root also works incredibly well on this tablet. It will be stuck on Android 4.4.2, so it is a little outdated, but seems to work rather well. It was designed for gaming, so it is pretty powerful for as old as it is.
Linux – keep it simple.
AlaskaLinuxUser said:
Just in case others have this problem and arrive here....
I recently got a Nabi Big 20 HD tablet to use as a camera viewer in a nursery at our church. The only problem was, when I turned it on, it kept giving me an error, stating that I had to hook up to the wifi, and that the FUHU servers had a problem. Essentially, since Fuhu went out of business, you can’t connect to the fuhu servers.
Since you can’t connect to the servers, setup can’t be completed, and this 20″ tablet became a 20″ paperweight. Obviously, that would not do, so I figured out how to use fastboot mode, TWRP, and the advanced file manager to delete the unneeded junk to make the tablet functional again. Below are my instructions, performed from a Linux computer. You could do this from Windows as well, if you download the right tools.
Before you begin, you will need the TWRP recovery image, which you can get from here: http://www.mediafire.com/folder/rul6liygr1rw3/Nabi_big_20_hd_tablet or from https://forum.xda-developers.com/android/development/recovery-nabi-bigtab-hd-20-t3035372
Power off the tablet.
Hold the volume up and power on buttons, and release them when you see the menu options.
NOTE: This is actually fastboot mode!
Perform an OEM unlock
[email protected]:~$ fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 13.625s]
finished. total time: 13.625s
[email protected]:~$
After this it reboots and starts up again, so power off the tablet.
Hold the volume up and power on buttons again, release them when you see the menu options.
NOTE: Once again, this is actually fastboot mode!
Flash the recovery image.
[email protected]:~/Downloads$ fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (8646 KB)...
OKAY [ 0.313s]
writing 'recovery'...
OKAY [ 0.314s]
finished. total time: 0.627s
[email protected]:~/Downloads$
From the still open menu, use the volume keys to scroll down to “recovery mode” and press the power button once to choose it. NOTE: it will show the NABI screen, then reboot into TWRP. Unfortunately, ADB does not work in this version of TWRP.
Go to “Mount” and check “System” and then click to disable MTP.
Press the home key or back key to get back to the main menu.
Click “Advanced”.
Click “file manager”.
Scroll to “priv-app” and select it.
Click on each of these items and choose to delete them:
fuhu_addapps2.apk
fuhu_appzone2.apk
fuhu_drmmanagerservice.apk
fuhu_nabiaccountmanager.apk
fuhu_nabiupdater.apk
–Personally, I just deleted all “fuhu” apps in this folder, but I think you only need those ones.
Then in the “app” folder, delete all the fuhu apps. Yes, I’m pretty sure you need to delete all of these ones.
Select the home or back button to get to the main TWRP screen.
Reboot to system.
Enjoy!
NOTE: It should start up, and may go through the Google setup (if you never started it before), and then will drop you off in “parent mode”.
At this point, I recommend installing a regular launcher, such as Trebuchet, Apex launcher, Nova launcher, etc. I used Apex launcher personally, because you can “hide” unwanted apps, and I use it to hide the unwanted Nabi apps. You should be able to see the Chrome browser in the parent mode window, use that to download the apk for the launcher you want (or use the Google account if you set up an account).
Once a launcher is installed, press the home key, and choose to always use the launcher you installed. You can now use this tablet as a regular Android tablet.
TWRP does have the option to install SuperSU and root the device. That’s completely up to you. Kingo Root also works incredibly well on this tablet. It will be stuck on Android 4.4.2, so it is a little outdated, but seems to work rather well. It was designed for gaming, so it is pretty powerful for as old as it is.
Linux – keep it simple.
Click to expand...
Click to collapse
Woah, wasn't expecting to see you here.
Thanks for that guide, had one as well but had since sold it
Thanks - the guide helped me unbrick my Nabi Big Tab 20"
AlaskaLinuxUser said:
Just in case others have this problem and arrive here....
I recently got a Nabi Big 20 HD tablet to use as a camera viewer in a nursery at our church. The only problem was, when I turned it on, it kept giving me an error, stating that I had to hook up to the wifi, and that the FUHU servers had a problem. Essentially, since Fuhu went out of business, you can’t connect to the fuhu servers.
Since you can’t connect to the servers, setup can’t be completed, and this 20″ tablet became a 20″ paperweight. Obviously, that would not do, so I figured out how to use fastboot mode, TWRP, and the advanced file manager to delete the unneeded junk to make the tablet functional again. Below are my instructions, performed from a Linux computer. You could do this from Windows as well, if you download the right tools.
Before you begin, you will need the TWRP recovery image, which you can get from here: http://www.mediafire.com/folder/rul6liygr1rw3/Nabi_big_20_hd_tablet or from https://forum.xda-developers.com/android/development/recovery-nabi-bigtab-hd-20-t3035372
Power off the tablet.
Hold the volume up and power on buttons, and release them when you see the menu options.
NOTE: This is actually fastboot mode!
Perform an OEM unlock
[email protected]:~$ fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 13.625s]
finished. total time: 13.625s
[email protected]:~$
After this it reboots and starts up again, so power off the tablet.
Hold the volume up and power on buttons again, release them when you see the menu options.
NOTE: Once again, this is actually fastboot mode!
Flash the recovery image.
[email protected]:~/Downloads$ fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (8646 KB)...
OKAY [ 0.313s]
writing 'recovery'...
OKAY [ 0.314s]
finished. total time: 0.627s
[email protected]:~/Downloads$
From the still open menu, use the volume keys to scroll down to “recovery mode” and press the power button once to choose it. NOTE: it will show the NABI screen, then reboot into TWRP. Unfortunately, ADB does not work in this version of TWRP.
Go to “Mount” and check “System” and then click to disable MTP.
Press the home key or back key to get back to the main menu.
Click “Advanced”.
Click “file manager”.
Scroll to "system" and select it.
Scroll to “priv-app” and select it.
Click on each of these items and choose to delete them:
fuhu_addapps2.apk
fuhu_appzone2.apk
fuhu_drmmanagerservice.apk
fuhu_nabiaccountmanager.apk
fuhu_nabiupdater.apk
–Personally, I just deleted all “fuhu” apps in this folder, but I think you only need those ones.
Then in the “app” folder, delete all the fuhu apps. Yes, I’m pretty sure you need to delete all of these ones.
Select the home or back button to get to the main TWRP screen.
Reboot to system.
Enjoy!
NOTE: It should start up, and may go through the Google setup (if you never started it before), and then will drop you off in “parent mode”.
At this point, I recommend installing a regular launcher, such as Trebuchet, Apex launcher, Nova launcher, etc. I used Apex launcher personally, because you can “hide” unwanted apps, and I use it to hide the unwanted Nabi apps. You should be able to see the Chrome browser in the parent mode window, use that to download the apk for the launcher you want (or use the Google account if you set up an account).
Once a launcher is installed, press the home key, and choose to always use the launcher you installed. You can now use this tablet as a regular Android tablet.
TWRP does have the option to install SuperSU and root the device. That’s completely up to you. Kingo Root also works incredibly well on this tablet. It will be stuck on Android 4.4.2, so it is a little outdated, but seems to work rather well. It was designed for gaming, so it is pretty powerful for as old as it is.
Linux – keep it simple.
Click to expand...
Click to collapse
This was perfect. I could not figure out how to get this device into FastBoot until I read your post today. The only tweak I had to make I added in line above was after I went to filemanager I had to select "system" before selecting "privapp".
hexagon_founder said:
This was perfect. I could not figure out how to get this device into FastBoot until I read your post today. The only tweak I had to make I added in line above was after I went to filemanager I had to select "system" before selecting "privapp".
Click to expand...
Click to collapse
Glad it helped!
And thanks for the note, yes, priv app is under system, and I forgot to mention that! [emoji3]
Sent from my Sony Xperia XA2 Ultra with Android 10
Hi, can you explain how you got into fastboot mode, or post a video? I am holding the plus sign button and the power button, but all that happens is the Nabi Bigtab flashes a few times, then stays dimly lit. It never loads any information, nothing about fastboot. Thanks.
EDIT: I figured it out. You have to press - the negative sign and the power button, NOT the plus sign, to get to the menu where you can choose recovery mode. THAT is the fastboot menu. It wasn't clear from the instructions. Make sure the tablet is hooked up when you do this and it should display on your PC as a "Fastboot" device.
I would appreciate help, my attempts are failing on this step using the nabilab64 drivers, minimal ADB, and this command:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
BT20A00000211140829 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>
fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.015s
I am using a USB 2.0 hub and a 3.0 plug. Same results. Also tried a different PC.
Thank you.
CCrusader said:
I would appreciate help, my attempts are failing on this step using the nabilab64 drivers, minimal ADB, and this command:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
BT20A00000211140829 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>
fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.015s
I am using a USB 2.0 hub and a 3.0 plug. Same results. Also tried a different PC.
Thank you.
Click to expand...
Click to collapse
CCrusader said:
Hi, can you explain how you got into fastboot mode, or post a video? I am holding the plus sign button and the power button, but all that happens is the Nabi Bigtab flashes a few times, then stays dimly lit. It never loads any information, nothing about fastboot. Thanks.
EDIT: I figured it out. You have to press - the negative sign and the power button, NOT the plus sign, to get to the menu where you can choose recovery mode. THAT is the fastboot menu. It wasn't clear from the instructions. Make sure the tablet is hooked up when you do this and it should display on your PC as a "Fastboot" device.
Click to expand...
Click to collapse
Odd, on mine it is the positive (+ up) volume button. Maybe it varied with different year models?
As for the adb command issue with Windows, I'm not sure, I use Linux... sorry I can't be more help.
Edit: perhaps try full adb, instead of minimal version?
Sent from my Sony Xperia XA2 Ultra with Android 10
AlaskaLinuxUser said:
Odd, on mine it is the positive (+ up) volume button. Maybe it varied with different year models?
As for the adb command issue with Windows, I'm not sure, I use Linux... sorry I can't be more help.
Edit: perhaps try full adb, instead of minimal version?
Sent from my Sony Xperia XA2 Ultra with Android 10
Click to expand...
Click to collapse
I'll try it. What version of ADB were you using and where did you get yours?
What version of the Nabi driver did you use? Does Linux support it natively?
I am using Windows 10. What version of Linux were you using?
Doing this for a customer so I'd like to figure out how to get this done. This has been a bumpy process so far.
Thanks.
CCrusader said:
I'll try it. What version of ADB were you using and where did you get yours?
What version of the Nabi driver did you use? Does Linux support it natively?
I am using Windows 10. What version of Linux were you using?
Doing this for a customer so I'd like to figure out how to get this done. This has been a bumpy process so far.
Thanks.
Click to expand...
Click to collapse
I used Ubuntu 18.04, and installed adb and fastboot from the Ubuntu repository. I did not need any drivers, as Ubuntu Linux was able to talk to fastboot right out of the box. Literally, the above steps was all I did.
Not bashing Windows, but Android runs a Linux kernel, and most Linux distributions can work with it much easier than Windows.
You can download a Ubuntu live CD and install adb and fastoob on your live run to do the job, if you don't want to install Ubuntu on a computer.
Hope that helps.
Sent from my Sony Xperia XA2 Ultra with Android 10
I got ubuntu and ran it off a live USB. Had to enable the app universe in software center, then installed ABP and fastboot. It unlocked the OEM and allowed flashing like a charm. Thank you. I hope this info helps someone else out, especially the minus sign rather than the plus sign.
CCrusader said:
I got ubuntu and ran it off a live USB. Had to enable the app universe in software center, then installed ABP and fastboot. It unlocked the OEM and allowed flashing like a charm. Thank you. I hope this info helps someone else out, especially the minus sign rather than the plus sign.
Click to expand...
Click to collapse
Glad it worked out! [emoji3]
Sent from my Sony Xperia XA2 Ultra with Android 10
I cannot get my WIndows 10 pc to recognize the big tab as an adb device. It is in fastboot mode (Start, Power off, and Recover mode menu) and I have installed all proper adb and fastboot drivers as well as tried using NabiLab and Mehtuus Nabi Root to install any sort of drivers. The tablet will either appear as "Unknown USB Device (Device Descriptor Request Failed)" or as "Fastboot" with the little exclamation mark and triangle next to it.
I have also tried booting into a live linux installation and get the same issue: adb will not detect the device.
I got a 24" paper weight...
I am in the same page, just got my 24" and could not pass the update page until I mess up the entire system.
Anyone here still got the stock ROM for the 24?
I found this somewhere but not sure what it is.
crazytiger1983 said:
I am in the same page, just got my 24" and could not pass the update page until I mess up the entire system.
Anyone here still got the stock ROM for the 24?
I found this somewhere but not sure what it is.
Click to expand...
Click to collapse
I'm also looking for files for the 24" version. Did you figure out what this file was for?
I have good news and bad news.
I somehow got the ROM file but its not from NABI, its from INFOCUS.
The problem is the could not get google play work.
Maybe someone here would have better idea what is wrong with it.
crazytiger1983 said:
I have good news and bad news.
I somehow got the ROM file but its not from NABI, its from INFOCUS.
The problem is the could not get google play work.
Maybe someone here would have better idea what is wrong with it.
Click to expand...
Click to collapse
So the file you attached in your post from March is the in focus flash files?
No, this is the one
crazytiger1983 said:
No, this is the one
Click to expand...
Click to collapse
Thanks. I just recently purchased one of these and am waiting for it to arrive. I don't know what state it will be in when I receive it. So what is the file for then from back in March?
It looks something like this: prog_emmc_firehose_8909_alc2.mbn
I don't know exactly what I did. I just flashed TWRP and booted in to it just to see if it was working, When I was done, I went to choose a partition to boot into, the first one said it had no operating system, I chose the second one which TWRP said had an OS. After that, the phone went dead and won't turn on. When I connect the phone to my PC, and go into device manager, the phone is listed as:
Qualcomm HS-USB QDLoader 9008. ADB doesn't see the phone, but QFIL does. I need the programmer file as well as a "rawprogram" file and a "patch0" file to flash the phone with QFIL.
Before I flashed TWRP, I unlocked the bootloader. I've unlocked the bootloader and flashed TWRP before and never had this happen.
Does a brand new phone only have the OS installed on one partition?
Could the programmer file be somewhere in the rom? In the sparsechunk files maybe?
Can the phone charge when its in this comatose state?
My nightmare began on Sunday night. I was waiting for a bus and a girl asked me to use the phone. While she was pretending to dial, a guy who she said was her brother(but probably wasn't) starts walking towards us. When he got close, she gave him the phone and they start running. I chased them and the guy says give me the passcode or I'll smash the phone. I said no and he smashed it on the ground and throws it over a fence. Then they ran back to the bus stop and stole my bike and ran away. I was able to recover the SD and SIM cards the next day. I have my phone backed up on the SD card.
What do you guys think their plan was? To steal my bicycle or my phone? Surely they knew the phone was useless without access to it. I could've rode away on my bike instead of chasing them. Before this all happened, they were standing across the street apparently casing me. I was doing something on my phone, so I didn't really notice them. Its not like they were professional thieves. They were just a couple of black kids around 20 years old from the ghetto. If they had a plan, it didn't make sense.
Heat84 said:
It looks something like this: prog_emmc_firehose_8909_alc2.mbn
I don't know exactly what I did. I just flashed TWRP and booted in to it just to see if it was working, When I was done, I went to choose a partition to boot into, the first one said it had no operating system, I chose the second one which TWRP said had an OS. After that, the phone went dead and won't turn on. When I connect the phone to my PC, and go into device manager, the phone is listed as:
Qualcomm HS-USB QDLoader 9008. ADB doesn't see the phone, but QFIL does. I need the programmer file as well as a "rawprogram" file and a "patch0" file to flash the phone with QFIL.
Before I flashed TWRP, I unlocked the bootloader. I've unlocked the bootloader and flashed TWRP before and never had this happen.
Does a brand new phone only have the OS installed on one partition?
Could the programmer file be somewhere in the rom? In the sparsechunk files maybe?
Can the phone charge when its in this comatose state?
My nightmare began on Sunday night. I was waiting for a bus and a girl asked me to use the phone. While she was pretending to dial, a guy who she said was her brother(but probably wasn't) starts walking towards us. When he got close, she gave him the phone and they start running. I chased them and the guy says give me the passcode or I'll smash the phone. I said no and he smashed it on the ground and throws it over a fence. Then they ran back to the bus stop and stole my bike and ran away. I was able to recover the SD and SIM cards the next day. I have my phone backed up on the SD card.
What do you guys think their plan was? To steal my bicycle or my phone? Surely they knew the phone was useless without access to it. I could've rode away on my bike instead of chasing them. Before this all happened, they were standing across the street apparently casing me. I was doing something on my phone, so I didn't really notice them. Its not like they were professional thieves. They were just a couple of black kids around 20 years old from the ghetto. If they had a plan, it didn't make sense.
Click to expand...
Click to collapse
Your device is in EDL Mode, it will charge in this state, also there is very little drain on the battery in this mode.
Motorola bundles these files as blankflash(es)
Try these
https://mirrors.lolinet.com/firmware/moto/racer/blankflash/
When you install a rom on a Moto device with a/b system you need you to follow this
Pre-install instructions
sd_shadow said:
Your device is in EDL Mode, it will charge in this state, also there is very little drain on the battery in this mode.
Motorola bundles these files as blankflash(es)
Try these
https://mirrors.lolinet.com/firmware/moto/racer/blankflash/
sd_shadow said:
Your device is in EDL Mode, it will charge in this state, also there is very little
Click to expand...
Click to collapse
Click to expand...
Click to collapse
sd_shadow said:
Your device is in EDL Mode, it will charge in this state, also there is very little drain on the battery in this mode.
Motorola bundles these files as blankflash(es)
Try these
https://mirrors.lolinet.com/firmware/moto/racer/blankflash/
Click to expand...
Click to collapse
When I run blank-flash.bat, I get:
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
I don't know how the double quote happened and I don't know how to view the raw code to delete it right.
Heat84 said:
When I run blank-flash.bat, I get:
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
I don't know how the double quote happened and I don't know how to view the raw code to delete it right.
Click to expand...
Click to collapse
Try this
Moto G6 XT1925-6 "bricked" from normal use--blankflash not working
Hi all, My girlfriend's Moto G6 XT1925-6 (purchased via Best Buy, never rooted/modded) got slow one day, I recommended rebooting and then it never came back. The only signs of life are that when plugged into a computer or charger. the white...
forum.xda-developers.com
sd_shadow said:
Try this
Moto G6 XT1925-6 "bricked" from normal use--blankflash not working
Hi all, My girlfriend's Moto G6 XT1925-6 (purchased via Best Buy, never rooted/modded) got slow one day, I recommended rebooting and then it never came back. The only signs of life are that when plugged into a computer or charger. the white...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried that and I still get: ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
I read somewhere that Windows could somehow be interfering with the process. How can I do this in Linux? How do I get Linux Mint to see the phone and how do I know that its being seen?
I never expected to get help this fast! Thanks everybody.
So nobody knows where to find the files I need for QFIL?
Here is a page that talks about Sahara protocol errors and how to fix them. I'm not exactly sure which one applies to me: https://blog.hovatek.com/how-to-fix-sahara-fail-error-in-qfil/
I have a rawprogram file and a patch0 file, but I don't know if they will work with my phone.
I figured out that you can reboot the phone by holding the power button(by watching it disappear and reappear in Device Manager). When I run blank-flash.bat right after rebooting, I get this:
Code:
[ -0.000] Opening device: \\.\COM11
[ 0.001] Detecting device
[ 0.002] ...cpu.id = 286 (0x11e)
[ 0.002] ...cpu.sn = 1010000641 (0x3c336301)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.009] ...filename = programmer.elf
[ 0.009] Sending programmer
[ 0.131] Handling things over to programmer
[ 0.131] Identifying CPU version
[ 0.131] Waiting for firehose to get ready
[ 3.213] ...SM_SAIPAN 2.0
[ 3.214] Determining target secure state
[ 3.219] ...secure = yes
[ 3.307] Configuring device...
[ 3.317] Skipping UFS provsioning as target is secure
[ 3.317] Configuring device...
[ 3.483] Flashing GPT...
[ 3.483] Flashing partition with gpt.bin
[ 3.485] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->find_first_package()->not found
[ 3.486] Check qboot_log.txt for more details
[ 3.486] Total time: 3.487s
[ 3.487]
[ 3.487] qboot version 3.86
[ 3.487]
[ 3.487] DEVICE {
[ 3.487] name = "\\.\COM11",
[ 3.487] flags = "0x144",
[ 3.487] addr = "0x28FD74",
[ 3.487] sahara.current_mode = "0",
[ 3.487] api.buffer = "0x2570020",
[ 3.487] cpu.serial = "1010000641",
[ 3.487] cpu.id = "286",
[ 3.487] cpu.sv_sbl = "0",
[ 3.487] cpu.name = "SM_SAIPAN",
[ 3.487] storage.type = "UFS",
[ 3.487] sahara.programmer = "programmer.elf",
[ 3.487] module.firehose = "0x24D1248",
[ 3.487] api.firehose = "0x67D948",
[ 3.487] cpu.ver = "512",
[ 3.487] cpu.vername = "2.0",
[ 3.487] fh.max_packet_sz = "1048576",
[ 3.487] fh.storage_inited = "1",
[ 3.487] }
[ 3.487]
Now I get a different error which you see at 3.485.
I didn't feel like playing around anymore so I took it to Best Buy(where I bought it from).
While they wouldn't fix it, they actually allowed me to exchange it for another one. I chose an open box one (that was probably returned for a stupid reason since its in brand new condition) so I wouldn't have to wait a week for a new one. I also got a $74 refund(to make the exchange even). I never thought I would make out this good(especially since I didn't choose the tech support option when I bought it).
What's gonna happen with the one I gave them? Are they gonna send it back to Motorola? Or just recycle/scrap it? It would be really sad not to fix it since just needs a simple re-flash.