Hi Guys,
i have a Sony Tablet S (first version, not Xperia) with 4.0.3 r5a (prerooted with AiO and old hidden.img) and it gets stuck on every second reboot, that means:
- Tablet is powered off
- Power on Tablet
- Tablet stuck on Sony logo (Logo refresh one time as you can see on the screen)
- Hold Power for 10 seconds to power down
- Tablet is powered off
- Power on Tablet
- Tablet boots normally
- Reboot Tablet from adb shell or app or just reboot manually (power off/power on)
- Tablet stuck on Sony Logo
- Power off 10 seconds
- Power on
- Tablet boots normally
........ and so on
What i have tried:
- Downgrade to 4.0.3 r1
- Connect via adb while stuck (not possible, adb does not recognize the device in this state)
- Wipe data (through recovery mode)
- Tried to find some log files which gives information (failed badly, logcat only produces output when tablet is already booted, no other logfile found)
Any ideas what could be the reason or what i should check?
Btw, the tab works perfect once it has booted up.
Keep on rockin'
Sony tablets have 2 boot partitions, one of yours is corrupt so the tablet boots to the other one. I think Condi's flasher can fix it, because it flashes both
Sent from my Nexus 4
lopezk38 said:
Sony tablets have 2 boot partitions, one of yours is corrupt so the tablet boots to the other one. I think Condi's flasher can fix it, because it flashes both
Sent from my Nexus 4
Click to expand...
Click to collapse
This is true, or since you have old recover you can use condi's double flash. If you use flasher please install the new recovery as well so it doesn't mess anything up.
I just reflashed 4.0.3 r5a with the actual AiO but so far the problem persists. Flashing went through flawlessly except the stuck on sony logo on the reboots and also the wipe after flash went through with no problems. Device is rooted and working, but still stuck on every second reboot.
Any other ideas?
Keep on rockin'
EDIT: I also tested it now with Flasher 3.0 (not AiO but also from condi) where i chose option 1 4.0.3 r5a wifi+3g and also flashed old recovery (option 2). I had no problems in the update process but the problem is still there.
i got same problem at 4.0
flash stock rom(root-able ver) then root it,the system is ok.
i guess aio tool have some bugs with none us regsions(my is china)
check your regaion.zip,file content,version and permition
Use his flasher tool, not the AiO
@robin
What exactly should i check on region.zip, anything special to look out for?
@lopezk38
As you might have read i also tried with the flasher tool, it wrote both partitions (current system and second system) but the problem persists.
Any other ideas how to fix this?
Keep on rockin'
Still nobody with an idea?
Just flashed custom_prerooted_doubleFLASH_R5A_nbx03_016-ota-121116077.zip from condi's thread @ http://forum.xda-developers.com/showthread.php?t=2020911 but still no luck, always stuck on second boot.
Although i had at least a little bit success with flashing 3.2.1 via AiO, after flashing it and getting stuck on reboot i wiped data in recovery mode and was able to boot at least once into 3.2.1, but after reboot i got stuck again and on second reboot it booted back to 4.0.3
At least that tells me that it is possible to boot from the partition, but something is still wrong.
I really appreciate all the help and the work from you guys.
On another note, i'm pretty firm with shell commands (long time linux user), anything i could try to check via adb shell?
Keep on rockin'
Corrupted for sure on the second boot partition, if double flashing does not help then something is really wrong with the second partition.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Corrupted for sure on the second boot partition, if double flashing does not help then something is really wrong with the second partition.
Click to expand...
Click to collapse
Leaves the question if there is a way to repair it, maybe by copying an image from the working partition with dd to the bad partition. I don' want to give up yet
DudemeisterAT said:
Leaves the question if there is a way to repair it, maybe by copying an image from the working partition with dd to the bad partition. I don' want to give up yet
Click to expand...
Click to collapse
Exactly same issue here since i rooted the device with last AIO 6.4 tool. Still searching for a solution too.
In the meantime i tried two more things to fix this problem.
First i copied the working partition to the not working partition with dd
dd if=/dev/mmcblk0p3 of=/dev/mmcblk0p2
The writing of the partition went through with no problems but it did not help at all. In my last effort to get system0 working again i tried flashing the OTA update (knowing that i will loose adb shell in recovery), but to my surprise after finishing the update successfully i was stuck with the same problem and a working adb shell. It seems OTA was flashed to system0 but is still not able to boot from it
I am running out of ideas and thinking about buying a new tablet (definitlely NOT a Sony Device anymore). Hopefully someone has another idea.
DudemeisterAT said:
In the meantime i tried two more things to fix this problem.
First i copied the working partition to the not working partition with dd
dd if=/dev/mmcblk0p3 of=/dev/mmcblk0p2
The writing of the partition went through with no problems but it did not help at all. In my last effort to get system0 working again i tried flashing the OTA update (knowing that i will loose adb shell in recovery), but to my surprise after finishing the update successfully i was stuck with the same problem and a working adb shell. It seems OTA was flashed to system0 but is still not able to boot from it
I am running out of ideas and thinking about buying a new tablet (definitlely NOT a Sony Device anymore). Hopefully someone has another idea.
Click to expand...
Click to collapse
I have the same problem, have you found a solution?
Sadly i was not able to fix it, i even tried to let the battery run out completely (was my last hope) but no change at all. I am thinking of sending it back again to sony for repair, cause now I am absolutely out of ideas, i think i tried everything possible.
Keep on rockin'
Sent from my Sony Tablet S using xda app-developers app
Any updates on this problem... BUMP
Sent from my Galaxy Nexus using Tapatalk 4
Sadly no, anyway i use my sgs4 more than the sony, much better Hardware just smaller screen. If there is a tab with the same or better specs (like sgs 4) i will buy a new one and give the sony to my brother. Farewell sony, i have enough of your crap.
Sent from my GT-I9505 using xda app-developers app
I have the same problem ! Any help would be greatly appreciated !
Did you try the things written in this thread?
Sent from my GT-I9505 using xda app-developers app
I don't know if there are still people interested in this but i finally got my tablet working again normally and booting up everytime.
Today i powered on the tablet after loading it fully and realised that there was no wifi anymore, i couldnt even enable the wifi adapter itself. After some other issues, including loosing root, i tried to reflash my backup. I went to recovery and selected the zip to flash which resulted in the "error in base sku" message. I tried different rom files which i had saved (custom signed, officialy signed) and none of them seemed to work. Rooting the device also did not work anymore, even if i tried manually executing all the commands, mostly i just got shut down by permission denied.
Anyway, after failing to try and flash the rom named signed-nbx03_016-ota-121116095.zip i luckily got the idea of renaming it to update.zip and put it in the root of the external sd card. I went back to recovery mode and selected the update.zip, flashing started and went through completely. The tablet rebooted and finished installing the rom and i ended up on the standard ics screen. I then took condis AiO and went to root the tablet and after the tablet rebooted it surprisingly booted again normally and after a quick check with super su i knew it was rooted. I did a couple of reboots with and without cable/ac adapter attached and now i am sure, it boots up every single time.
It looks like that the filename update.zip might tell the tablet to flash differently than with another name, at least i like to hope so. Maybe it helps someone out there with the Tab S.
Funny sidenote, two weeks ago i bought a SM-T805
Have fun
Related
Hi all,
I had rooted my nook tablet using snowball mod about a week ago and I loaded CWM on to the emmc using indirect's one-click recovery flash app. It was all working fine.
I wanted to return to stock and so put the 1.4.0 zip on my sdcard and rebooted. But it went straight to CWM. So I remembered i had to restore the stock recovery and rebooted and flashed stock recovery. only this time, I used the updated version of the one-click app (the updated version of 26th Jan) and hit reboot to recovery. This caused my NT to be in a boot loop ever since.
I have tried the 8 failed reboot method to initiate a factory reset but it didn't work. I also tried using the Nook Recovery Fix but i can't get to install the drivers since if I connect the NT to my computer, it keeps rebooting over and over again and I can't get to show for longer than 2 secs in device manager to install the drivers for Windows. (I was using it on Ubuntu till now).
My NT just turns on, the black screen n logo shows (The "With adobe reader" screen) however it doesn't go any farther than that. It just shuts down. The white nook screen does not even show. It's like it's going through multiple failed reboots without me holding down any buttons. Any help from you guys is greatly appreciated. Thanks.
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Data Injures said:
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Click to expand...
Click to collapse
Thanks a lot for your suggestion! I just spent a half hour on the phone with B&N customer service and they agreed to ship out a replacement device. The rep said it was a hardware failure that was causing it to act like that. I was a bit surprised at that. I'm not sure she knew what she was talking about. Anyway I had bought mine off craigslist. And now I'm getting a new device so I guess I can't complain. But I'll try later tonight to restore this one using the bootable CWM you linked to. Thanks again.
Follow Up
Just thought of posting a follow up. The bootable CWM method worked. I was able to fix the recovery. Most certainly not a HW problem like the tech claimed. It's working fine now.
I'm glad to hear that! Now if I have the same problem in the feature I can just follow my own advice. Lol
Sent from my DROIDX using XDA App
So I have basically the same problem. My girlfreinds nook was rooted but the OTA update stopped the root from being effective. I tried the sd card revert to 1.4.0 and I hade the problem with the "n" butting not working. When i tried the 8x reset the nook went into an endless boot loop where I see the back screen and the next white screen flashes for like 2 seconds and then reboots. I tried to make the CWM SD card but it still just reboots. My question is that since i never had the CWM mod installed am I pretty much hosed or am I doing something wrong?
What are you using to make the CWM SD card? I strongly recommend using GParted either from a Linux live image or there is a GParted live image you could use. When it works correctly, the bootable SD card that should stop the boot loop.
But why did the boot loop problem occur in the first place ?
sailerph said:
But why did the boot loop problem occur in the first place ?
Click to expand...
Click to collapse
From what I know of, if you install stock recovery and hit the reboot to recovery button, it initiates the stock recovery which then causes the error. Though I don't know the reason behind nor what's causing the problem, just relaying what I have read around the forums.
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Denmmurray said:
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Click to expand...
Click to collapse
Hm I actually unrooted my nook a couple of times to play with it. I reinstalled the stock recovery from the app on multiple occasions, but instead of clicking reboot to recovery, I ran the one click unroot and never ran into any trouble.
Hey everyone, thanks in advanced for looking.
I purchased a rooted HTC 4g View and it was running stock GB with S-OFF. It was rooted with Revolutionary.
I decided it was time to upgrade to HC but I had no knowledge of flashing roms or anything like that and hired someone to do it for me. From what I can tell he flashed "Desenced" and it was great! Then the problems started..
The tablet every so often just went to the loading screen of HC start up. It started doing it very rarely to every hour or so and I decided I would just buy another table because of the inconstant behavior.
Now the tablet won't turn on unless plugged in and only boots into ClockworkMod Recovery v5.8.1.5
When I try to wipe everything and reflash desenced, it says Flash Complete! Then reboots, goes straight to CWM again.
I've tried using command prompt while the tablet is plugged in but no matter what I mount, it won't respond to the computer.
Please help, I'd love to have this tablet back.
Okay I found the solution!
I used the adb and the drivers for the stock rom (3.2) from sdk manager.
In CWM Recovery I mounted /system in order for my computer to recognize the tablet.
Once there, I kept rebooting the tablet using the command, "adb reboot oem-78" until the corrupted rom booted up enough for me to be able to use the RUU.
I then followed the instructions on this thread
Everything is now great and I've learned a lot. Thanks everyone for looking and if anyone has any questions, I'd be more than happy to share.
Cheers!
I had done the original root/gapps install on this. Then had problems with gapps. So I went back into TWRP and I had a restore called stockunrooted. I restore it, and when I go to reboot it says "Warning, No OS installed". Sure enough, it boots to a little Nabi logo with no motion. And just sits there. I used TWRP file manager and don't see any files in /boot after I do a restore. /boot and /system seem to restore instantly. I'm good with PC's, Networks, and Linux, but not Android hacks. Is there something I can download, push with ADB, then load with TWRP that will fix me up? I think that's how I got the STOCKUNROOTED that is already there though
Got Nabi2
Rooted with jmz?? method and also installed his gapps
Nabi wouldn't power on right without reset hole after a week or 2
Restored stockunrooted, worked fine, no more power on problem, but no root or gapps
Rooted per jmz method, worked, no gapps.
Wanted to install gapps, so restored stockunrooted again, now nothing
At least TWRP works. It's wifes though, and she isn't into just using it for TWRP.
- Joe
JoeLansing said:
I had done the original root/gapps install on this. Then had problems with gapps. So I went back into TWRP and I had a restore called stockunrooted. I restore it, and when I go to reboot it says "Warning, No OS installed". Sure enough, it boots to a little Nabi logo with no motion. And just sits there. I used TWRP file manager and don't see any files in /boot after I do a restore. /boot and /system seem to restore instantly. I'm good with PC's, Networks, and Linux, but not Android hacks. Is there something I can download, push with ADB, then load with TWRP that will fix me up? I think that's how I got the STOCKUNROOTED that is already there though
Got Nabi2
Rooted with jmz?? method and also installed his gapps
Nabi wouldn't power on right without reset hole after a week or 2
Restored stockunrooted, worked fine, no more power on problem, but no root or gapps
Rooted per jmz method, worked, no gapps.
Wanted to install gapps, so restored stockunrooted again, now nothing
At least TWRP works. It's wifes though, and she isn't into just using it for TWRP.
- Joe
Click to expand...
Click to collapse
Flash this in twrp:
http://www.androidfiles.org/securekey.php?file=Nabi2/JmzNabi2Stock_OLD.zip
Sent from my One X using xda app-developers app
GuyIncognito721 said:
Flash this in twrp:
http://www.androidfiles.org/securekey.php?file=Nabi2/JmzNabi2Stock_OLD.zip
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Ok, I got that. Having problems getting TWRP to see it. I tried from SD card, tried copying it into sd-ext, sdcard, external_sdcard, sdcard/twrp/backups. No luck. If I click Install from sdcard it shows me /sdcard/root.zip so I tried putting it in there but no luck when I click recovery. I tried setting permissions on the zip to 777. What on earth am I doing wrong. I spent about an hour with google searching before I came back here. I'm on TWRP v2.2.2.1
- Joe
JoeLansing said:
I had done the original root/gapps install on this. Then had problems with gapps. So I went back into TWRP and I had a restore called stockunrooted. I restore it, and when I go to reboot it says "Warning, No OS installed". Sure enough, it boots to a little Nabi logo with no motion. And just sits there. I used TWRP file manager and don't see any files in /boot after I do a restore. /boot and /system seem to restore instantly. I'm good with PC's, Networks, and Linux, but not Android hacks. Is there something I can download, push with ADB, then load with TWRP that will fix me up? I think that's how I got the STOCKUNROOTED that is already there though
Got Nabi2
Rooted with jmz?? method and also installed his gapps
Nabi wouldn't power on right without reset hole after a week or 2
Restored stockunrooted, worked fine, no more power on problem, but no root or gapps
Rooted per jmz method, worked, no gapps.
Wanted to install gapps, so restored stockunrooted again, now nothing
At least TWRP works. It's wifes though, and she isn't into just using it for TWRP.
- Joe
Click to expand...
Click to collapse
i hope ya wasnt using the mic hole on the bottom of the Unit
http://www.nabitablet.com/specs/nabi2
IF i were you i would Search the forum "nabi 2"
you will find a lot of post with downloads and things that people have done to help get their nabi 2 up and running.
HTH
I used the reset hole and I've already downloaded all the jmz files and a few more. I've read about Nabi here for hours. My last try was restoring JMZ_OLD to get back to factory. Still no WiFI. Then I tried installing the WiFI_Fix. Now it just shows a spinning Nabi logo. I rooted my 4th one today using the new Nabi Lab which I really like! My wife's is the only one that is a problem child. Funny thing is the other 3 were bought at Walmart, hers was bought at GameStop. I think from reading the Cannot Turn on WiFi is a version problem between the drivers and the kernel, but not sure. I really want to try Nabi Lab on it but I think it is old Nabi software at this point, and Nabi Lab says I should be fully updated to run it. But I can't update it without WiFi...grrrrrrrrr. Is there anything I can do to restore it to stock including stock kernel and drivers? Who knows, maybe the WiFI has a hardware problem? But I doubt it. If I use JMZ_Old, then the 2 OTA update files, then ??? I'm not sure I've tried that yet. I wipe everything between attempts. 3 more posts and I can go thank the gentelman that made Nabi Lab in that thread and tell him I tested it and it worked fine.
- Joe
I wonder if you have a Different Nabi 2 then i do ?
coz the only hole I have that looks like a reset hole is for the mic
http://forum.xda-developers.com/showthread.php?t=2050365&highlight=nabi
has a few different downloads like a striped rom a full untouched version and a full de-odexed version.
maybe try that one
.---UPDATE---
New Rom available.
Completely stock.
Not even De-Odexed.
Update 37.
SHOULD fix WiFi issues.
Flash using directions at top of post substituting this zip for the one used in the directions.
PureStockU37.zip
that is the updated 1.9.37 Current at the time of this post
Ok, I'm a moron. My reset hole is the mic, which is now pretty dead...:crying: The good news is Nabi Lab fixed my WiFi and soft brick problems. I had tried about every image out there including that one you suggested. Using Nabi Lab and flashing the hmm All Original - Won't Boot or something like that fixed it. Since I never use the mic I'm ok. I could probably replace it if I wanted to, but I'll give it a rest before I break it again.. I have 3 Nabi's, and 2 Uniden tablets. I killed one of the Unidens. The screen got worse and worse. I popped it apart and tried to reattach the 2 wires to the screen half. It started smoking and doesn't power on.. Now I might take the battery off it and see if I can solder it into the other Uniden to get longer life. I hope it doesn't get hot.
Eric Karz said:
I wonder if you have a Different Nabi 2 then i do ?
coz the only hole I have that looks like a reset hole is for the mic
http://forum.xda-developers.com/showthread.php?t=2050365&highlight=nabi
has a few different downloads like a striped rom a full untouched version and a full de-odexed version.
maybe try that one
.---UPDATE---
New Rom available.
Completely stock.
Not even De-Odexed.
Update 37.
SHOULD fix WiFi issues.
Flash using directions at top of post substituting this zip for the one used in the directions.
PureStockU37.zip
that is the updated 1.9.37 Current at the time of this post
Click to expand...
Click to collapse
that's good you got the nabi working
Now that nabi with the bad speaker ... i wonder if you can use the speakers from the dead Uniden in the nabi 2 ?
here is a thread where the nabi 2 was open up
http://forum.xda-developers.com/showthread.php?t=2024105&highlight=nabi
If you try the battery project or the speaker replacement - be neat to see pictres of it....lol
Speaker was a beer typo.. I meant the mic. I'm an old man and have no use for croaking at people over the interweb with a microphone so I'm ok.. I started a thread someplace about the Uniden tablets. I checked back and it's like 9 pages long with geeks installing Ubuntu and everything else on them. I was amazed! I'm going to get real and get an Onda V972 soon I hope. Now that I have enough posts here I will probably start a thread about buying one of them.
- Joe
Eric Karz said:
that's good you got the nabi working
Now that nabi with the bad speaker ... i wonder if you can use the speakers from the dead Uniden in the nabi 2 ?
here is a thread where the nabi 2 was open up
http://forum.xda-developers.com/showthread.php?t=2024105&highlight=nabi
If you try the battery project or the speaker replacement - be neat to see pictres of it....lol
Click to expand...
Click to collapse
Help brick
Sorry my english.
I was trying to install the GAPPS on nabi2 and messed up.
The kernel recovery screen appears with a exclamation android open.
In normal boot the screen is locked in logo nabi.
I do not have TWRP installed.
When I select fastboot protocol recognizes the PdaNet and appears as a device in windows mtp unknown.
Is there any chance to recover? Could guide me the way?
There is some recovery via APX?
RegisRicci said:
Sorry my english.
I was trying to install the GAPPS on nabi2 and messed up.
The kernel recovery screen appears with a exclamation android open.
In normal boot the screen is locked in logo nabi.
I do not have TWRP installed.
When I select fastboot protocol recognizes the PdaNet and appears as a device in windows mtp unknown.
Is there any chance to recover? Could guide me the way?
There is some recovery via APX?
Click to expand...
Click to collapse
Need to reinstall TWRP with fastboot.
Download a ROM image and restore it in TWRP.
There is an APX way but so far untested and not needed for where you are at.
Thanks for the help, after a snack could reconfigure.
I'm trying to install Freedom but is difficult. There is not enough system memory.
I updated to 2.1, but I think I'll go back to 2.05.
Hello,
I, ve been reading xda for many years and had many android devices (recently SGSII for 2 years). I have quite an experience flashing roms, using recoveries etc... But this time on HTC One X+ (international) I really need XDA users help, thats why I decided to write this post.
I have a new unbranded HOX+, managed to unlock its bootloader, flash TWRP (for my version of HOX+) and from there flash superuser.zip. All worked ok (didn't produce any errors). Root is ok. But after a while, when I turned on the phone and tried to install an APK from PlayStore or read gmail - phone rebooted.
And it stills constanly do this whatever I try to do. Phone reboots whithout any change. I cannot relock bootloader, wipe, flash, install apps or copy files to phone. Every time I try to simpy use it, it just reboots with state reverted to the moment of first boot after rooting. If I leave it alone it still reboots, but after a while.
Adb and fastboot connections are available , but it looks like they are unable to commit any change. Stock rom with TWRP. I can boot to TWRP, but nothing there give a result. I can wipe, format, fix permissions, it all says operation went ok, but after a reboot, my system is unchanged.
Fastboot flashes of boot.img or recovery.img report success, but after reboot kernel / recovery aren't changed. Same with relocking bootloader, it reports that has been locked, and in bootloader mode i still see big, pink "UNLOCKED". So I also cannot flash RUU.
It seems I am unable to normally use my brand new smartphone and change anything.
Does anyone have a clue how to fix it?
Please help. I desperately need suggestions.
Thanks.
Htc ONE X+ Help!!
7virage7 said:
Hello,
I, ve been reading xda for many years and had many android devices (recently SGSII for 2 years). I have quite an experience flashing roms, using recoveries etc... But this time on HTC One X+ (international) I really need XDA users help, thats why I decided to write this post.
I have a new unbranded HOX+, managed to unlock its bootloader, flash TWRP (for my version of HOX+) and from there flash superuser.zip. All worked ok (didn't produce any errors). Root is ok. But after a while, when I turned on the phone and tried to install an APK from PlayStore or read gmail - phone rebooted.
And it stills constanly do this whatever I try to do. Phone reboots whithout any change. I cannot relock bootloader, wipe, flash, install apps or copy files to phone. Every time I try to simpy use it, it just reboots with state reverted to the moment of first boot after rooting. If I leave it alone it still reboots, but after a while.
Adb and fastboot connections are available , but it looks like they are unable to commit any change. Stock rom with TWRP. I can boot to TWRP, but nothing there give a result. I can wipe, format, fix permissions, it all says operation went ok, but after a reboot, my system is unchanged.
Fastboot flashes of boot.img or recovery.img report success, but after reboot kernel / recovery aren't changed. Same with relocking bootloader, it reports that has been locked, and in bootloader mode i still see big, pink "UNLOCKED". So I also cannot flash RUU.
It seems I am unable to normally use my brand new smartphone and change anything.
Does anyone have a clue how to fix it?
Please help. I desperately need suggestions.
Thanks.
Click to expand...
Click to collapse
Hi, you can change the recovery? TOUCH tries CWM Recovery v6.0.2.7 (CONFIRMED WORKING CHARGING MODE OFF). Try it, I recommend Android Revolution HD 7.0 + boot.img forum for 7.x find it, good luck and excuse my English.
Flash recovery with HTC One X + All-In-One Toolkit V3.0 [7-16-2013] [PERM ROOT] [Noob-Proof], sorry if I can not do much, I hope to see this more and serve you better help.
thacruz said:
Hi, you can change the recovery? TOUCH tries CWM Recovery v6.0.2.7 (CONFIRMED WORKING CHARGING MODE OFF). Try it, I recommend Android Revolution HD 7.0 + boot.img forum for 7.x find it, good luck and excuse my English.
Flash recovery with HTC One X + All-In-One Toolkit V3.0 [7-16-2013] [PERM ROOT] [Noob-Proof], sorry if I can not do much, I hope to see this more and serve you better help.
Click to expand...
Click to collapse
Hey, .
Sadly, recovery does not change. I am able to flash it through fastboot, it reports succes, but after reboot I still see my old TWRP.
Thats my issue, my phone is magical, nothing seems to affect its state
Thanks for your advice!
Htc ONE X+ Help!!
7virage7 said:
Hey, .
Sadly, recovery does not change. I am able to flash it through fastboot, it reports succes, but after reboot I still see my old TWRP.
Thats my issue, my phone is magical, nothing seems to affect its state
Thanks for your advice!
Click to expand...
Click to collapse
one more attempt, try doing it on another PC, and that the Toolkit is in C:. And that the folder has a short name, such as C :/ Toolkit or something, someone else help us, is an impressive smarthphone.
thacruz said:
one more attempt, try doing it on another PC, and that the Toolkit is in C:. And that the folder has a short name, such as C :/ Toolkit or something, someone else help us, is an impressive smarthphone.
Click to expand...
Click to collapse
Thanks for ideas, but it still does not work. Phone reverts its state. It's trully magical. Every time it reboots to the moment just after rooting. I have never seen anything like it before. Bootloader is always unlocked and memory chip state cannot be changed.
At least I haven't figure out how to do it yet
Anyone, please help!
EDIT:
A tried ADB sideload today, but after the file is sideloaded it can't be flashed - TWRP considers it corrupted and it vanishes after rebooting - AS EVERY CHANGE
I hope I didn't ruined my phone the first hour I got it, and XDA members could still help me. PLEASE
Hmm, it seems like everything fails to write to the emmc chip on your device, I would try to take it to a shop that does JTAG fixes, it could be a defective memory/emmc chip, sadly HTC will probably make you pay full price
Sent from my Desire HD using Tapatalk 4 Beta
humzaahmed155 said:
Hmm, it seems like everything fails to write to the emmc chip on your device, I would try to take it to a shop that does JTAG fixes, it could be a defective memory/emmc chip, sadly HTC will probably make you pay full price
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi, I think also it's is the explanation for HOX+ radio lacks, permanent screen locks after the sleep, etc... fails in my AT&T's unlocked HOX+, defective emmc or emmc firmware.. It´s possible?
You also can see it: http://forum.xda-developers.com/showthread.php?t=2404393
Here is a little background;
I'm new to the android world and this is my first tablet using it. I received the tablet under the terms that its mine, if I can fix it. THE TABLET So the research begins. The original problem with the tablet: everything would crash after unlock screen, including loader. The tablet does not have any kind of visual recovery mode using the hard buttons. At this time I did not know about any of the tools that I probably could of used to save the stock firmware. When I hit Google with "Cruz velocity micro t510" not much came up, so I spent about a day trying all sorts of different terms with that. There was not even a place to download firmware from cruz, they say wifi is mandatory to upgrade, from within the tablet... I finally ran into a post somewhere where someone said the cruz t510 is an allwinner a10 in disguise. They went on to say that all you need to do is use Livesuit and flash 'sun4i_crane_T05a_v1.5_mxc6225' img from eken website then from there you can use the compatability zip and upgrade to cm10.
So all was good. The t05a firmware there works perfect on it, like the guy said. I kept that on there for a day before I went on to CyanogenMod.
Here is where I am stuck; (Tired of googling, please help )
I decide to try AOKP and CM10 using http://forum.xda-developers.com/showthread.php?t=1821398 and one for AOKP too with t05a-v1_compatibility_1.2.x.zip. And http://forum.xda-developers.com/showthread.php?t=2189640 for recovery mode. I learned how to setup and use ADB with command prompt here.
So I install CWM using ADB shell and reboot into recovery using the sh file. I first folowed the steps to install AOKP and all goes smoothly until I reboot.
I get a notice saying "Damaged SD Card, You may need to reformat" and I realize that it is talking about the internal disk space. I try to reformat and the same notice will appear again or I will have to go in Settings>Storage and Mount SDcard, only to be told no, it is damaged. So I got scared and re-flash back to the eken stock firmware with livesuit. Guess what, sdcard mounted and working again. Then I go on to repeat the upgrade but with CM10 this time. Same result.
I have gone back to the stock image and retried many times. I tried with all three partition versions of that CWM I use, even though I knew it was 10, or so adb shows. I also tried partitioning and formmating with CWM, many times, each a little different.
Short, Sweet, and Simple version;
THE TABLET
Eken a90 stock firmware using livesuit -> SDCard works fine
CM10 or AOKP with t05a-v1_compatibility_1.2.x.zip using CWM 6.0.2.8 -> SDCard damaged
If anyone could help I would very much appreciate it. I need a break from all the research, I'm going to play gtav and hope someone has a solution for me.
I'm trying to upgrade my T510 from original manufacturers specs and could sure use whatever files uou have