[Q] Diagnosis pse: settings and files lost on reboot - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

I have bought a second-hand Galaxy Tab which will not keep changes in settings or any uploaded files or IDs after switch off and restart.
This means I cannot root it, as any uploaded files with Odin are lost on restart.
Can anyone help me please? I have tried all the usual resets to no avail.
FG

No-one interested in a tricky problem challenge???
ForeignGadger said:
I have bought a second-hand Galaxy Tab which will not keep changes in settings or any uploaded files or IDs after switch off and restart.
This means I cannot root it, as any uploaded files with Odin are lost on restart.
Can anyone help me please? I have tried all the usual resets to no avail.
FG
Click to expand...
Click to collapse
Hmm, I thought this might intrigue the experts, but to no avail.
Where the hell do I go for an answer to this problem: rooting cannot be done as flashed files will be lost on reboot.

ForeignGadger said:
Hmm, I thought this might intrigue the experts, but to no avail.
Where the hell do I go for an answer to this problem: rooting cannot be done as flashed files will be lost on reboot.
Click to expand...
Click to collapse
Hmm have you really odined and see the files replaced? Can you boot into recovery do a full wipe and odin a stock or custom rom
Sent from my GT-P7510 using Tapatalk

animatechnica said:
Hmm have you really odined and see the files replaced? Can you boot into recovery do a full wipe and odin a stock or custom rom
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Hi. Thanks for getting back.
I have gone up and down the forums for ideas. (for over 3 days now).
The story so far:
I have tried to flash the overcome .tar file for my model using odin 1.83, but get a red box and a Fail! : error 0X140005. I followed the Overcome guide VERY carefully, got the yellow COM box, put the right file in the right box, but when I hit the start button, it fails.
I can boot into "Download". I have tried restore after wiping the cache.
With normal power up, the OS seems to work partially, in that I can do all the things I want to do, but all the settings, WiFi passwords, uploaded files etc disappear on reboot, and any uninstalled programmes re-appear. It seems that it won't permanently write to, or erase from, "long term" memory.
Before this,I have done a full cache wipe and factory restore but no difference.
Thoughts:
a) I am wondering if a previous occupant has tinkered with it and messed up the memory partitions? is it all RAM?
b) As it is stuck, it is stuck with USB debugging disabled. this will be maintained on reboot: could this interfere with Odin?
Any suggestions would be very, very gratefully accepted.
FG

ForeignGadger said:
Hi. Thanks for getting back.
I have gone up and down the forums for ideas. (for over 3 days now).
The story so far:
I have tried to flash the overcome .tar file for my model using odin 1.83, but get a red box and a Fail! : error 0X140005. I followed the Overcome guide VERY carefully, got the yellow COM box, put the right file in the right box, but when I hit the start button, it fails.
I can boot into "Download". I have tried restore after wiping the cache.
With normal power up, the OS seems to work partially, in that I can do all the things I want to do, but all the settings, WiFi passwords, uploaded files etc disappear on reboot, and any uninstalled programmes re-appear. It seems that it won't permanently write to, or erase from, "long term" memory.
Before this,I have done a full cache wipe and factory restore but no difference.
Thoughts:
a) I am wondering if a previous occupant has tinkered with it and messed up the memory partitions? is it all RAM?
b) As it is stuck, it is stuck with USB debugging disabled. this will be maintained on reboot: could this interfere with Odin?
Any suggestions would be very, very gratefully accepted.
FG
Click to expand...
Click to collapse
Dude i ask this in another forum you posted, did you use odin to install recovery or not? if you did then just boot into recovery and wipe all - then flash galaxytab or any flashable roms that way.
Sent from my GT-P7510 using Tapatalk

As I said in the second paragraph: I tried to use odin to install recovery, but got the big red square. The file did not transfer.

ForeignGadger said:
As I said in the second paragraph: I tried to use odin to install recovery, but got the big red square. The file did not transfer.
Click to expand...
Click to collapse
No your second paragraph said you flashed overcome. Not recovery
So if odin is not installing recovery can you boot into fastboot? Power off then press power n volume down then go to fastboot mode and install recovery that way. Check this thread for info. . http://www.galaxytabforums.net/forum/galaxy-tab-10-1-general-discussions/1044-my-galaxy-tab-10-1-wont-power-up.html
Then flash a cwm flashable ROM
Sent from my GT-P7510 using Tapatalk

OK, thanks for the steer and your patience. I'll get to work.
I'll report back (eventually!).
(Please remember that there is an awful lot of jargon and TLA's to learn for us newcomers, even if willing).
Regards, FG

ForeignGadger said:
OK, thanks for the steer and your patience. I'll get to work.
I'll report back (eventually!).
(Please remember that there is an awful lot of jargon and TLA's to learn for us newcomers, even if willing).
Regards, FG
Click to expand...
Click to collapse
Lol i hear you i was there too
Sent from my GT-P7510 using Tapatalk

animatechnica said:
Lol i hear you i was there too
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
hi again; well no success so far.
- I downloaded and installed SDK (software development kit: for other noobs like me)
- I downloaded and installed recovery.img, and installed the google USB drivers from the extras
- I checked that the fastboot.exe, adb.exe (android debug bridge) and recovery.img were all in the platform tools folder.
- got into "download":- odin mode
- plugged in the tab and tried to launch "adb start-server" from cmd screen
(I was in the right directory at the command line), but no cigar: nada.
- I went back and did the PDAnet routine, but still no joy, no devices shown
there were no error messages either, which made me think the usb was not communicating with the tab.
To try this out I used Kies to transfer a photo file to the tab, and viewed on the tab it after disconnecting, so tranfers do take place.
Sure enough, after rebooting, the file was gone, like all the other settings and changes made in the past.
I also tried adb when the tablet was on and I had checked usb debugging. In this case, adb recognised the device and returned the serial number.
It does not do this when in cwm mode as it will not remember to keep debugging on when I power down.
Any other ideas anyone? can I switch debugging on from the command line before I try to recover?
FG, (now getting a sore head and worrying if I have p***d my money up the wall.)

Funny, when things get really tough, the helpers disappear.
Still no solution.

Oh dear: silence again.

ForeignGadger said:
- got into "download":- odin mode
- plugged in the tab and tried to launch "adb start-server" from cmd screen
(I was in the right directory at the command line), but no cigar: nada.
- I went back and did the PDAnet routine, but still no joy, no devices shown
there were no error messages either, which made me think the usb was not communicating with the tab.
To try this out I used Kies to transfer a photo file to the tab, and viewed on the tab it after disconnecting, so tranfers do take place.
Sure enough, after rebooting, the file was gone, like all the other settings and changes made in the past.
I also tried adb when the tablet was on and I had checked usb debugging. In this case, adb recognised the device and returned the serial number.
It does not do this when in cwm mode as it will not remember to keep debugging on when I power down.
Any other ideas anyone? can I switch debugging on from the command line before I try to recover?
FG, (now getting a sore head and worrying if I have p***d my money up the wall.)
Click to expand...
Click to collapse
AFAIK you won't get a response in ADB when the tablet is in download mode but you should when the tablet is in CWM recovery mode.
If it were me I'd odin a stock factory recovery to the device and a stock factory rom for it. Then i'd boot into stock recovery and do the factory reset to see if that cleans things up. You should probably link to the source of the files you're downloading as well as provide specific model of your device so people can verify that you're flashing the right files.

I'm totally confused by your steps here
you went to odin mode and used adb? or did you go into fastboot and adb the recovery?
step by step here
a quick overview of it is to get your tab into ODIN mode and use ODIN to reload a copy of the stock image to your tab. This erases all of your previous data but you can reinstall those later. But at least it gets you back to a working tab - Note this is for the 7510 - the wifi tab
1) Download this file - MEGAUPLOAD - The leading online storage and file delivery service
2) extract the file
you should have the following
a file called GT-P7510_USB_Driver_v1_3_2360_0-Escape - this file is the USB driver for your PC, if you don't have the driver installed already, run this
a folder named Odin3 v1.85 - this contains the ODIN executable file
a folder named KME Odin - which contains 2 files - android_fastboot_emmc_full_p4_16G_32G.pit" and a "P7510XABKME_P7510UEKME_HOME.tar"
3) Power down the tab
4) press POWER and Volume Down at the same time until it powers up and you should see 2 logos - USB and triangle (note the retail wifi version might show 2 different logos, android on right and bag on left - left is recovery and right is Odin/download)
5) press volume down to move the selection to the triangle (or the icon on the right)
6) press volume up to lock in selection. You are now in ODIN/download mode
assuming all your drivers are installed to your PC, plug in the tab via the USB to your PC
run the ODIN executable
only Auto-reboot and F.reset Time should be ticked
after a minute, the ID:Com box should turn yellow -if not you may have driver issues (try this driver http://drivers.softpedia.com/progDo...SB-Driver-for-Windows-x86-Download-96692.html)
7) tick PDA and click the PDA button and navigate to the KME Odin folder and select "P7510XABKME_P7510UEKME_HOME.tar"
8) select the PIT button and navigate to the KME Odin folder and select the "android_fastboot_emmc_full_p4_16G_32G.pit"
9) Select START
it should start writing the image to your tab and once done, should reboot you back into stock
in case you want to go ahead and flash 3.2 -
use this pit file - http://forum.xda-developers.com/attachment.php?attachmentid=784889&d=1321486916
and use this for the PDA http://hotfile.com/dl/135008863/06c...EKMM_P7510XABKMM_P7510UEKMM.rar.html?expire=1
if it asks you for Password for the 3,2 file use : sampro.pl
when resorting to odin and first booting up, you might get asked for a password, the way around this is to
a) power off,
b) press power n volume down until you get 2 icons left is recovery right is download.
c) press volume down to select recovery icon then volume up to lock it, you should then see the recovery menu
d) then use volume buttons until wipe data/factory reset is highlighted press power to do it
e)after its done wiping, select reboot n you should be ready
Now the key thing here is installing the right drivers - after installing teh driver, connect the tab and see if the drivers are installed - go to your pc control panel and check if you get a triangle with an exclamation point. If there is, right click on it and select update driver, then manually choose device - navigate through and find the Android or samsung device (cant remember the name off the top of my head)
if you get stuck, report on which part you got stuck on - currently it seems like you're mixing and matching different steps so it is a little confusing
ForeignGadger said:
hi again; well no success so far.
- I downloaded and installed SDK (software development kit: for other noobs like me)
- I downloaded and installed recovery.img, and installed the google USB drivers from the extras
- I checked that the fastboot.exe, adb.exe (android debug bridge) and recovery.img were all in the platform tools folder.
- got into "download":- odin mode
- plugged in the tab and tried to launch "adb start-server" from cmd screen
(I was in the right directory at the command line), but no cigar: nada.
- I went back and did the PDAnet routine, but still no joy, no devices shown
there were no error messages either, which made me think the usb was not communicating with the tab.
To try this out I used Kies to transfer a photo file to the tab, and viewed on the tab it after disconnecting, so tranfers do take place.
Sure enough, after rebooting, the file was gone, like all the other settings and changes made in the past.
I also tried adb when the tablet was on and I had checked usb debugging. In this case, adb recognised the device and returned the serial number.
It does not do this when in cwm mode as it will not remember to keep debugging on when I power down.
Any other ideas anyone? can I switch debugging on from the command line before I try to recover?
FG, (now getting a sore head and worrying if I have p***d my money up the wall.)
Click to expand...
Click to collapse

Hi again, sorry to confuse you but I was following your suggestions in post #7 of this thread. when I got to step 5 of that post, I got no response from the device: installed PDAnet to get over the driver issue. and no joy.
When trying to install .tar or PIT files I get a big red box, even though the yellow COM box looks good.
When trying the data erase/ factory reset option in the "Download" mode, I get the error message "Can't access to /system/csc/XEU/system.
Steps 7/8/9 in your post above do not work: I have tried them a few times.
Sorry, I have run out of options, and thank you for your help.

Related

[Q] Unbrick Nextbook Premium 7?

I need some serious help... I think I bricked my Nextbook Premium 7. I compiled a custom ROM and forgot to included a launcher. Didn't realize it until after I flashed it. My tablet is stuck in a bootloop and only way to shut it down is with the reset [pin hole] button. Power button does nothing except start it up. I have already tried to put the stock update.img on an external SD hoping it would boot from there, but it did not. I am not sure what to do next, I have looked all over google and xda. Please help!
Thank you in advance!
Do you have a custom recovery installed? Did you try installing it threw fastboot files and cmd prompt on computer?
Please hit the thank you button if i helped!
techno-update said:
Do you have a custom recovery installed? Did you try installing it threw fastboot files and cmd prompt on computer?
Please hit the thank you button if i helped!
Click to expand...
Click to collapse
There ins't a custom recovery installed, this device flashes by detecting an update.img and askes to install it. It doesn't get past what would be considered the kernel screen. This tablet doesn't work like a standard android phone. There are no hard buttons except the power button, so attempting to get into any recovery is not possible. It also doen't boot enough to add any files to it.
Sounds like your screwed. Sorry.....
Please hit the thank you button if i helped!
check out this link
http://forum.xda-developers.com/showthread.php?t=1410862&page=9
Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Fi..._Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)
Help !!
Please help, got the tablet yesterday NEXT7P12 YF091211085 by flashing the official site was a brick, the tablet will not turn on, the computer does not see it.
screen moved after installing rom
Hi, i don't know if I'm on the right place but if anyone can help me, please I haw the Nextbook 7 premium and have instaled costum rom on it, but after rebooting my screen position has moved from right to left 2 cm and from up to down 1 cm , so my screen is moved I don't know why I have try to install 3 other rom and factory firmware but the screen is still moved or should I say cut. Any ideas? please I have try to google it but no luck...
I no longer have my np7 but I did try just about every ROM for it. Never have I had or seen an issue like this, and in truth I can't think of what the issue may be.
There are different np7 variants and some don't play nice with custom ROMs (built sept 2012 and older lose WiFi) so you might have a model that can only use one software due to hardware/firmware change.
There never was much development for the np7 here, I think finlessbob and others are still working on it at freaktab.com maybe see if they can help
Sent from my Nexus 4 using xda premium
d33dvb said:
Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Fi..._Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)
Click to expand...
Click to collapse
Your link not working? Send alternative link please!

bricked 1a - yet cannot connect via ADB. Help!!

first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
perch_44 said:
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
Click to expand...
Click to collapse
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
flumpster said:
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
Click to expand...
Click to collapse
If that fails, I had the same issue with cwm, I installed twrp via fastboot and haven't had the problem of the file not showing up after adb push. Fustrating I know.... I tired everything I could think of in cwm multiple reboots different usb ports... on an on......
Please HELP CWM Roocovery Loop!!!
perch_44 said:
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
Click to expand...
Click to collapse
I am having the same exact problem. It started when I tried to restore my stock backup that I made using CWM 5.8.2.0 coming from the CM rom. I am stuck in the CWM recovery screen and cant get ADB to see the TF Prime. I just get error: device not found. How did you manage to push a zip if ADB wasn't seeing your device? I have been looking for a fix for the last week now.
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Danny80y said:
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Click to expand...
Click to collapse
How do I flash TWRP when Im stuck CWM?
hellshavoc said:
How do I flash TWRP when Im stuck CWM?
Click to expand...
Click to collapse
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Striatum_bdr said:
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Click to expand...
Click to collapse
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
hellshavoc said:
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
Click to expand...
Click to collapse
you hold the volume down until the screen starts, then you let go and wait
whycali said:
you hold the volume down until the screen starts, then you let go and wait
Click to expand...
Click to collapse
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
hellshavoc said:
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
Click to expand...
Click to collapse
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
It is confusing but just keep trying till you get it!! Once there go to the TWRP site they have the file and the fastboot commands all set in a guide.
I have exactly the same problem than you.
I had the fastboot/adb connection (I used to push the rom by adb), but i tried to install a wrong version on gapps. Since then, I'm stock in the recovery mode without adb/fastboot connection.
If you find a solution for that, pleaze post it !!
Striatum_bdr said:
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
Click to expand...
Click to collapse

HELP with problem with installing Viper+

Hello. I just got a HTC ONE X+ yesterday as my first smart phone, iv been using a basic nokia for around 20years lol I choose the HTC mainly because I saw a review of one using the Viper+ rom and love to customise my computers so thought this was right up my street.
I sat down today watched a couple of youtube videos & read a few tutorials, I unlocked the phone through the cmd and did the reset, all went smoothly as far as i was aware, I then went into settings and there was no developers options to select, I dumped the rom onto the storage, and went into the fastboot again since im following a step by step guide, I did the backup, wiped Wipe Cache, Dalvik, then when I went to Factory Reset it said failed, I thought ok ill try again after system, did that went back to FR again said failed. hhmm ok, went ahead with installing Viper and it started installing and said fail. so I went to reboot but told me their is no OP any more, so I tried to do a restore but it shows an empty folder, so now it only boots into the white HTC logo screen and sits there. I can get into the fastboot menu still, but when connected to a laptop it doesn't show up as a device so I cant view any folders or anything.
does anyone know where it went wrong and a way to correct this? it would be a big help to me, thank you
-Marc
you didn't say what recovery you got I suggest you to install TWRP 2.7.1.0 from here:
http://techerrata.com/file/twrp2/enrc2b/openrecovery-twrp-2.7.1.0-enrc2b.img
when you download that .img file install this toolkit, that you will download from here:
https://mega.co.nz/#!ZExEEBJL!jKoitltieeOIb8JV-cjqw9i4ldV1yXFUAf-q1W8-UUE
It's easy very easy to install you have option to install "Your own recovery" select that and press flash and select your .img that you download up, it will say in cmd 2 times Okay.
But before you flash, when you unzip this toolkit from .rar put it in "C:\" not in "C:\something\something & other things" becouse toolkit won't found .img.
After that you download 2.1.1 rom from here:
http://uploaded.net/file/tqmae0zd
and when you download the rom he will be named like ViperX_2.1.1 or something like that you rename it to just viperx.
When you did all that go into recovery wipe all, connect your phone to a PC go to device manager to portable devices and disable HTC One X+ if you don't do that adb won't recognized the phone. Then in recovery go to Advacned - Adb sideloade press that button and on PC through toolkit in section Extras select first option adb sideload press run, and select viperx.zip rom in toolkit folder or in "C:\" where you put it. Sideload will begin counting to 100% when it finish, rom will run automatically, rest is easy just next next pick what you want.
P.S
Don't forget to install latest htc drivers, and latest drivers for usb to avoid some conflicts becouse when sideloading adb won't recognized sometimes, that happends.
Thanks for the reply, I would of liked to have given this ago but now the tool kit keeps saying enable USB debugging first, which I cant do....anyway to do this without the original OS installed?
First of all there is THANKS button in left corner under avatar, so you can click on it instead of saying Thanks.
Second you don't need usb debugging mode in recovery go into recovery wipe all like I write in my first reply, install drivers first for HTC and do everything like i told you up there.

OTA Update Stuck in Recovery Mode_Error: Status 7(No Hard Keys-Volume Buttons)

Hello there,my Wave 8 HD+ stuck in android boot logo. I downloaded the wave8hd_20151105_v1.8 update thru wireless update and install, it says error in installing:
E:error in /mnt/internal_sd/adupsfota/update.zip
(Status 7)
Installation aborted.
My tablet is now in recovery mode and cant move highlight due to no volume buttons available,i can only select the "reboot system now" option.
Any other alternative for volume button so that i could just do the factory reset??
I also followed the detailed instruction on bluewave website on how to update the said Tablet thru PC but to no avail.
i emailed both the Telecom Company from where i get my Bluewave Tablet and the Bluewave Customer support but until now they stiil haven't replied yet.
thank you very much for your immediate reply.
-Jovi
jovirex said:
Hello there,my Wave 8 HD+ stuck in android boot logo. I downloaded the wave8hd_20151105_v1.8 update thru wireless update and install, it says error in installing:
E:error in /mnt/internal_sd/adupsfota/update.zip
(Status 7)
Installation aborted.
My tablet is now in recovery mode and cant move highlight due to no volume buttons available,i can only select the "reboot system now" option.
Any other alternative for volume button so that i could just do the factory reset??
I also followed the detailed instruction on bluewave website on how to update the said Tablet thru PC but to no avail.
i emailed both the Telecom Company from where i get my Bluewave Tablet and the Bluewave Customer support but until now they stiil haven't replied yet.
thank you very much for your immediate reply.
-Jovi
Click to expand...
Click to collapse
maybe try to use adb and try to push the firmware manually.. if they have a firmware download available
toolhas4degrees said:
maybe try to use adb and try to push the firmware manually.. if they have a firmware download available
Click to expand...
Click to collapse
I did use the software Rockchip Batch Tool v1.7 provided by Bluewave in their website,install the 33GT driver for my tab(Tab can now be seen by my PC and download the correct firmware update(using my serial number at the back of said tablet) still provided by Bluewave,but still error in upgrade..
i just want to know how to change the highlighted option in recovery mode so i can wipe/factory reset my Tablet disregarding the said update..
there is an option in recovery mode "recover system from back up" but i could not choose to highlight and select the option..
any alternatives for the volume button??Btw,the firmware provided by Bluewave is in ".img" format,not "zip"..
thank you so much for your reply..
-Jovi
i have the same problem, got an error after wireless update.. please help!
to fix this... use your otg cable and connect a usb mouse then reboot it once its reboot use the mouse to move into the recovery mode... wipe data and cache then select update adb sideload once inside the sideload press the power button until it reboot.. once you see the bluewave and its start to have a loading in the lower right corner.. voila... your tablet is fix ... hope it help u
ohgnevets said:
i have the same problem, got an error after wireless update.. please help!
Click to expand...
Click to collapse
wave 8hd+
jho_zep said:
to fix this... use your otg cable and connect a usb mouse then reboot it once its reboot use the mouse to move into the recovery mode... wipe data and cache then select update adb sideload once inside the sideload press the power button until it reboot.. once you see the bluewave and its start to have a loading in the lower right corner.. voila... your tablet is fix ... hope it help u
Click to expand...
Click to collapse
hello, jho_zep, thank you so much for your reply, i am now able to move the highlight to select using my mouse, but still when i try to update from ADB, it tells me to send package to the device etc.. and i also tried to press the power button, it wont reboot the system, it would only shutdown the system.. another thing, i still cant get rid of the system update. " installing system update" then error comes in, my android is down.. i tried wipe date/ factory reset, still nothing.
Thanks in advance
Do you already solve your problem? because I have now the same problem as this.
I have pressed the wireless update then it restarted and it says an Error status 7.
I don't know what to do and how to deal with this problem.
can you help me?
My nextbook tablet rk3026 has a partition named metadata that holds the recovery boot commands. You could possibly try to wipe it and do a factory reset. I don't think it actually gets mounted so you would need to find a file the same size as the partition and dd to it. Or back up your system with rockchip flash tool then using a hex editor replace all data in metadata image with zeros. Obviously be careful. Here is a tool download with included guide credits to finless at freaktab(not sure if he is here at xda) for posting it.
http://freaktab.com/forum/developme...p-your-rk-device-rom-with-the-new-rk-2-1-tool
as always BACKUP and know if you don't do it correctly you may get a brick.
thank you for the response Destructos. but that solution won't help for my freakin weird tab 33gt HD+.
I get frustrated now
Problem solved
first thing to do is make sure that you have already installed the rkchip_usb driver in your computer.
What are the requirements?
1st of course your Tablet and Cable Connector
2nd Finless ROM Flash Tool v1.37
3rd Rokchip BatchTool v1.7
4th the update image/firmware for your Bluewave 8 HD+ that is downloadable from their official website
Steps:
1. off your tablet and connect it to the computer
2. open the Finless Rom Flash, uncheck all the boxes
3. turn ON your Tablet (be attentive) and while the blue screen is starting you may NOTICE that the ROM FLASH TOOL detected your device, it says "RKAndroid Mass Storage USB". when you have read that, press immediately the "Reboot Flash mode" and your device will in black screen. but ROM Flash tool still detected your device as "RKAndroid Mass Storage USB "
4. Open the Batch Tool, (you must know how to use it) find your image, then you will notice that the CONNECTED DEVICES below have color green, in that case you may now Click UPGRADE. wait for a minute and booooom, you device is functionable again.
have a feedback if it is helpful.
P.S.
before I go to that steps, when I am stuck in RECOVERY MODE of my device, I Click the Recover from BACKUP then my tablet restarts and it turns to BOOTLOOP and repeatedly saying NO COMMAND.
PLDC said:
first thing to do is make sure that you have already installed the rkchip_usb driver in your computer.
What are the requirements?
1st of course your Tablet and Cable Connector
2nd Finless ROM Flash Tool v1.37
3rd Rokchip BatchTool v1.7
4th the update image/firmware for your Bluewave 8 HD+ that is downloadable from their official website
Steps:
1. off your tablet and connect it to the computer
2. open the Finless Rom Flash, uncheck all the boxes
3. turn ON your Tablet (be attentive) and while the blue screen is starting you may NOTICE that the ROM FLASH TOOL detected your device, it says "RKAndroid Mass Storage USB". when you have read that, press immediately the "Reboot Flash mode" and your device will in black screen. but ROM Flash tool still detected your device as "RKAndroid Mass Storage USB "
4. Open the Batch Tool, (you must know how to use it) find your image, then you will notice that the CONNECTED DEVICES below have color green, in that case you may now Click UPGRADE. wait for a minute and booooom, you device is functionable again.
have a feedback if it is helpful.
P.S.
before I go to that steps, when I am stuck in RECOVERY MODE of my device, I Click the Recover from BACKUP then my tablet restarts and it turns to BOOTLOOP and repeatedly saying NO COMMAND.
Click to expand...
Click to collapse
Why is it, when I do this, my tablet can't be detected by the software? I'm stuck on recovery mode. When it's on the blue logo, still does nothing.
I can only see my device when I look for it on Device Manager under Android Phone. Why is that? It doesn't show the "Other Devices". I've installed the driver but to no avail, still fails me. Please help. Thanks!

Used ODIN to install twrp but phone won't boot into recovery at all

I'm using SM-J510H
So I installed samsung drivers.
I even installed ADB and it's drivers (now i have samsung android in the device manager)
I downloaded TWRP for j53gxx:
https://eu.dl.twrp.me/j53gxx/
The .tar for odin (twrp-3.4.0-0-j53gxx.img.tar)
I did the OEM unlock and debugging thing I even got the notification that the computer was trying to access blah blah I did allow always.
Put the phone in download mode (Down + Home + Power)
Press up to enter download mode.
Connect the phone.
Untick reboot in odin.
Use the ap to select the correct file
Start success!
I try to reload into recovery tried so many different ways even the adb command to reboot into recovery. All I get is a little thing on the top left saying warranty bit recovery and then the screen is black.
It doesn't load into the default recovery it just stays black. I need to take the battery to rest...
I tried with adb but when i force it to load up into download mode (adb reboot bootloader)
adb doesn't recognize the phone anymore
I've now downloaded the android ask maybe that will solve things lol but does anyone have any advice please?
Damn ignore this wrong forum reposted in QandA
GoodKnight_IL said:
I'm using SM-J510H
So I installed samsung drivers.
I even installed ADB and it's drivers (now i have samsung android in the device manager)
I downloaded TWRP for j53gxx:
https://eu.dl.twrp.me/j53gxx/
The .tar for odin (twrp-3.4.0-0-j53gxx.img.tar)
I did the OEM unlock and debugging thing I even got the notification that the computer was trying to access blah blah I did allow always.
Put the phone in download mode (Down + Home + Power)
Press up to enter download mode.
Connect the phone.
Untick reboot in odin.
Use the ap to select the correct file
Start success!
I try to reload into recovery tried so many different ways even the adb command to reboot into recovery. All I get is a little thing on the top left saying warranty bit recovery and then the screen is black.
It doesn't load into the default recovery it just stays black. I need to take the battery to rest...
I tried with adb but when i force it to load up into download mode (adb reboot bootloader)
adb doesn't recognize the phone anymore
I've now downloaded the android ask maybe that will solve things lol but does anyone have any advice please?
Click to expand...
Click to collapse
First off, i would find your twrp maintainer. I wonder who he is
You have j510h, and you downloaded the j500h twrp. How do you expect me to help you beyond that?
palmbeach05 said:
First off, i would find your twrp maintainer. I wonder who he is
You have j510h, and you downloaded the j500h twrp. How do you expect me to help you beyond that?
Click to expand...
Click to collapse
Lol i realized not long ago updated my post in tbe q&a damn if you would have answered sooner would have saved me so much time.
Thanks for the reply though!

Categories

Resources