Hi, recently I Flashed my iconia a500 with cm10 jelly bean 4.1.2 bootloader v8. After one weel of awesome performance my tab is now dead, when I try to reboot it is stopping at the first screen from the bootloader without charging the os. In the recovery menu everithing is working perfect but when I try to reboot is always showing me the same : "skrilax_cz's bootloader v8 booting primary kernel image".
Could please some body help me?
Thanks!
momotizzati said:
Hi, recently I Flashed my iconia a500 with cm10 jelly bean 4.1.2 bootloader v8. After one weel of awesome performance my tab is now dead, when I try to reboot it is stopping at the first screen from the bootloader without charging the os. In the recovery menu everithing is working perfect but when I try to reboot is always showing me the same : "skrilax_cz's bootloader v8 booting primary kernel image".
Could please some body help me?
Thanks!
Click to expand...
Click to collapse
Something is wrong with the kernel boot in your setup. It can be anything, for example a weird looping script in init.d, corruption in the kernel partitin, whatever.
What I would do (I have a Iconia a500 in my household that I don't actively flash anymore) is the nuclear option: boot to recovery, wipe everything and reflash the rom. Maybe also refash the kernel if that isn't in the rom zip.
Zatta said:
Something is wrong with the kernel boot in your setup. It can be anything, for example a weird looping script in init.d, corruption in the kernel partitin, whatever.
What I would do (I have a Iconia a500 in my household that I don't actively flash anymore) is the nuclear option: boot to recovery, wipe everything and reflash the rom. Maybe also refash the kernel if that isn't in the rom zip.
Click to expand...
Click to collapse
HI Zatta, I reflashed different time some different rom and kernel but the result is not changing, I'm still in front of the starting screen but the rom is not charged. Any other suggestion? If I try to flash a new bootloader with nvflash is stop at the half of the procedure. Also if I try to restore an hold backup is not working. How can I fully restore the tab?
Ohoh, what made you think the bootloader was the problem?
Anyway, if you can boot to recovery, use that. Else, browse the forum to find help, for example in this thread :
http://forum.xda-developers.com/showthread.php?p=28777415
Taptalked u see .. əəs n pəʞlɐʇdɐʇ
I tried to reflash bootloader different time but no way. Now the Tab is start always/just in apx mode.
Any suggestion for a full reset or restore from apx mode?
You ****ed something up. Anyway, if your really can't boot into recovery anymore, follow this guide:
http://forum.xda-developers.com/showthread.php?t=1622425
and do the manual method. I hope you have saved you CPUID and SBK somewhere.. Further questions can better be asked in that thread also as I am not fully involved in that device anymore.
Related
hey guys, I don't know what happened to my Prime, but this is what I did:
I was on a Nexus 7 ported ROM and it was running fine. Tried to flash PARANOID ANDROID and failed. So I tried to flash Androwook, and now it's stuck on the splash screen. The only thing I can do is boot to the recovery (CWM). Is there anyway I can fix it? Is it bricked?
I am going to assume you have ADB working on your computer. Just download a new rom, your choice, and using the command
adb push C:\NAMEOFFILE \sdcard\Downloads
you don't have to put the file in the downloads folder, just an example. May need Gapps as well. Wipe and flash as normal.
JC0406 said:
hey guys, I don't know what happened to my Prime, but this is what I did:
I was on a Nexus 7 ported ROM and it was running fine. Tried to flash PARANOID ANDROID and failed. So I tried to flash Androwook, and now it's stuck on the splash screen. The only thing I can do is boot to the recovery (CWM). Is there anyway I can fix it? Is it bricked?
Click to expand...
Click to collapse
Read post 2 of the androwook thread and get twrp installed.
Make sure you do the ICS to JB upgrade before flashing a Jellybean TWRP. The correct bootloader is the most important part about twrp
And while you still have a chance and are still on the ICS bootloader do this. http://forum.xda-developers.com/showthread.php?t=1774352
It wont work once you have Jellybean
Hey guys!
Since I tried building Firefox OS -Boot2Gecko- on my Samsung Galaxy S2 (i9100) (FYI: I followed this walkthrough) , I'm having quite a hard time making my phone boot on any ROM I try to install. I still have an access to CWM Recovery and to the Download mode
* After failing to flash B2G's Gaia on my phone, I tried to flash the kernel back to the original one and to restore the CM 10.1 NIGHTLY backup I made before doing all this mess. No changes: stuck at CM's boot screen.
* Tried to get back to a stock firmware and ROM, stucks at boot screen ("Samsung Galaxy S II GT-I9100" screen), even after a wipe data/factory reset, wipe cache and wipe dalvik cache.
(In fact, I achieved to boot on a stock ROM once, but after some other manipulations to get my CM 10.1 back, I now can't get it to boot on any of them anymore.)
* I tried to follow the rooting + CyanogenMod walkthrough on CM's wiki, but the same happens: stucks on boot screen. However, after a wipe data, I reach CM's boot animation, which runs indefinitely.
* Right now I tried flashing with Siyah's Kernel, since the flash counter is not any of my concerns anymore. Whatever I try, I can't get anything to get past the "Booting the primary ROM" message.
However, I installed a stable CM9 on the secondary ROM and... it actually works. But even when cloning 2nd ROM to the 1st ROM, can't get the first to boot anyway.
I am not an expert in Android OS architecture, but could it be related to some kind of modifications made by B2G's build & flashing? Maybe some files in the /data or /system partitions have been altered and are not replaced when fllashing, leading to ROMs not loading up?
Any advice on this is welcome.
PS: English is not my main language, sorry if things aren't explained clearly. Tell me if you need any clarifications about it!
hey there,
i have a similiar problem.
i got the info to reflash it using ODIN.
one user told me, that maybe the NAND-RW could be corrupted....
so iam trying it right now...
good luck
Wipe kernel/rom data with a cleaning script. You can find them in dev sections.
Well I flashed it many times with Odin (or Heimdall when I was on Linux) and I saw no improvement.
I don't think my NAND-RW is corrupted, as I can still boot on Download or Recovery mode.
Just found this tutorial, is it worth the try?
Sakujou_Kei said:
hey there,
i have a similiar problem.
i got the info to reflash it using ODIN.
one user told me, that maybe the NAND-RW could be corrupted....
so iam trying it right now...
good luck
Click to expand...
Click to collapse
Well I flashed it many times with Odin (or Heimdall when I was on Linux) and I saw no improvement.
I don't think my NAND-RW is corrupted, as I can still boot on Download or Recovery mode.
Just found this tutorial, is it worth the try?
TheATHEiST said:
Wipe kernel/rom data with a cleaning script. You can find them in dev sections.
Click to expand...
Click to collapse
This one http://forum.xda-developers.com/showthread.php?t=1363738 (Kernel) and this one http://forum.xda-developers.com/showthread.php?t=2100558&highlight=script (ROM) ?
Ok so I tried the cleaning scripts I linked on my previous message, no changes. I can still boot on Siyah's second ROM, but can't get past the "Booting primary ROM" message.
Ideas anyone?
Hi,I have a transformer prime which was running on Energy Rom ICS 4.1.
Yesterday I thought of updating it to Energy JB rom.
The post said it needs updated bootloader as well so I downloaded the bootloader package (TWRP 2.5) but did not know that it formats the tablet completely.
So I flashed it but when it restarted the tab I saw Asus logo & blue progress bar & on top left it said formatting internal storage so I forced shutdown the tab by keeping power key pressed.
But now I am unable to install any ICS rom as it flashes the rom but gets stuck on the boot animation.
I tried installing Energy JB & Androwook JB rom but has lot of force close issues, camera doesnt work.
I tried installing TWRP 2.5 using fastboot but my laptop says usb device not recognised.
Downloaded naked universal usb driver but dont know what to do with them as there is no setup (exe or msi) file in that zip.
I even tried flashing older ics version of bootloader & repeated the whole procedure but doesnt help.
PLEASE HELP ME OUT. I CANNOT POST IN THE ENERGY ROM'S POST AS IT DOESNT ALLOW ME
ergauravpro said:
Hi,I have a transformer prime which was running on Energy Rom ICS 4.1.
Yesterday I thought of updating it to Energy JB rom.
The post said it needs updated bootloader as well so I downloaded the bootloader package (TWRP 2.5) but did not know that it formats the tablet completely.
So I flashed it but when it restarted the tab I saw Asus logo & blue progress bar & on top left it said formatting internal storage so I forced shutdown the tab by keeping power key pressed.
But now I am unable to install any ICS rom as it flashes the rom but gets stuck on the boot animation.
I tried installing Energy JB & Androwook JB rom but has lot of force close issues, camera doesnt work.
I tried installing TWRP 2.5 using fastboot but my laptop says usb device not recognised.
Downloaded naked universal usb driver but dont know what to do with them as there is no setup (exe or msi) file in that zip.
I even tried flashing older ics version of bootloader & repeated the whole procedure but doesnt help.
PLEASE HELP ME OUT. I CANNOT POST IN THE ENERGY ROM'S POST AS IT DOESNT ALLOW ME
Click to expand...
Click to collapse
You messed up by forcing shutdown but I think you know that now..
The only thing I can suggest is if you can still use TWRP then first go to wipe menu and format data, wipe system, wipe dalvik and then wipe cache.
Now try to install your rom.
If this still does not work then try getting the downgrade.zip from the hairybean thread and flashing it in twrp and then restarting and letting it fill all the blue line this time.
At this point you should be able to install a 4.1.1 rom so just try Hairybean 1.51 for now doing all the same wipes as before.
If this works then go and follow the same Energy rom instructions before but without killing the install.
Thanks but I have allready tried that
Hi, I have already tried downgrading bootloader from both Energy Rom thread as well as Androwook thread.
TWRP is still working on my tab & when I flashed downgrade.zip from Hairybean thread,it says successful but does'nt ask for restart,even after rebooting from twrp menu,it again restarts into twrp & i tried androwook ics rom but gets stuck on bootanimation same as Energy Ics based rom.
Any advice????
ergauravpro said:
Hi, I have already tried downgrading bootloader from both Energy Rom thread as well as Androwook thread.
TWRP is still working on my tab & when I flashed downgrade.zip from Hairybean thread,it says successful but does'nt ask for restart,even after rebooting from twrp menu,it again restarts into twrp & i tried androwook ics rom but gets stuck on bootanimation same as Energy Ics based rom.
Any advice????
Click to expand...
Click to collapse
First of all please stop flashing things. You are mentioning ICS and Jellybean and the new bootloader and different versions of TWRP that are only compatible with certain bootloaders. You will brick it if you are not careful if you haven't already.
Power off and then hold down the power button and volume down the same time. You should get into the bootloader menu with icons.
At the top left of the screen there should be some writing with a long number.
Tell me what that number is please and also tell me what icons are on the screen.
flumpster said:
First of all please stop flashing things. You are mentioning ICS and Jellybean and the new bootloader and different versions of TWRP that are only compatible with certain bootloaders. You will brick it if you are not careful if you haven't already.
Power off and then hold down the power button and volume down the same time. You should get into the bootloader menu with icons.
At the top left of the screen there should be some writing with a long number.
Tell me what that number is please and also tell me what icons are on the screen.
Click to expand...
Click to collapse
Hi, every time I switch on my tablet now, it goes into TWRP by default, even on pressing power + volume down buttons it does not show me any icons but straightaway boots into TWRP, I tried installing Androwooks JB Rom (which was buggy before but atleast working), but it again reboots into TWRP recovery by default, I did all the wiping before installing as well.
When I power on my tab, all I see is ASUS logo in middle & on top left it says "device is unlocked", then straight into TWRP recovery.
I think I have screwed up big time.
Please help
Hi Android experts!
I need some assistance fixing a problem I caused & am now stuck in a recovery boot loop.
- bought a Thomson QM734-8G tablet (Allwinner A13b clone), running Jellybean 4.2.2;
- PC interface worked fine in MTP and large storage modes;
- setup Android SDK & Java JDK on PC and communicate with tablet via ADB;
All OK so far
After a couple of days, I decided to replace stock recovery with ClockworkMod Recovery, so I could start messing about with the tablet.
I found the CWM 6.0.2.8 mod supposed to work with these tablets and, following instructions, determined it was indeed running on sun5i hardware and had 10 partitions (nandj) and downloaded the appropriate version.
I used ADB sideload to install CWM and everything appeared to work OK ... until I rebooted and found myself stuck in a never-ending cycle of CWM-based recovery bootloop
All I get is the CWM recovery console, with a few lines of error & the tablet will go no further.
E:can't mount /cache/recovery/command
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
Also, pretty much none of the CWM functions work properly and nothing will mount through the 'Mounts and Storage' section, although sideload mode still seems to work.
Attempts to use ADB sideload to install a different CWM or other recovery image have all failed, and LiveSuit and PhoenixSuit both have issues detecting the tablet (despite trying various versions of each & following instructions precisely), so I can't flash a replacement ROM to fix things.
At the moment, I just want to rip CWM out and go back to factory recovery mode and have a working tablet again!
Any suggestions on how to resolve this problem would be greatly appreciated
P.S. I think the Bootloader is locked and the tablet is unrooted. Superuser or SuperSU don't want to install properly. However, using ADB, it looks like I can get root access in shell (#).
Oh No!
I have the same problem! I was trying to sort the tablet out for a friends kid as it was acting up, tried to root using the Allwinner A13 generic android tablet 4.0.4 root method
but now I am stuck in a bootloop like you..
I have seen one other post about this from Jan 2013 and nobody has replied to it...I am imagining probably not many people have this tablet and basically, there is no solution...:crying:
I have a Samsung Galaxy S i9000 and it was simple to reinstall everything through CWM..On a Samsung Galaxy Young recently, it wasn't as easy as that but I made it through..but there doesn't seem to be download mode neither kernels for this device (since I guess it's not popular)..I hope we haven't ended up with a brick!! :crying::crying::crying:
Success! I have managed to sort it out y using LiveSuit 1.09 and Manta ROM 4.2.2
I think the problem either was that I was pressing + instead of - to enter adb recovery mode, thou I think it didn't make a difference perhaps...but I think the real problem was not finding the right ROM and Live Suit combo. Sometimes I would get a 0x162 error which is meant to mean an incompatible ROM (thou it did this on ROM that was advertised as stock!)
I think this Manta ROM works for a lot of people however, you may have problems with the touchscreen drivers for which you can have a look at [MOD] FaaastJB v2.5 A13 Allwinner with Jelly Bean 4.2.2 by Toxicro for trying the various touchscreen drivers. It worked for with no probs so I don't need to mess around with them but they are easy enought to install. Just click the run.bat file (usually) and it should do everything for u.
Good Luck!
bootloop allways STuck in cwm mode after inSTALL CWM RECOVERY
was trying to install CWM RECOVERY on my A13 tablet n now i think its BRICKED!!!
every time i turn it on it goes back to the stupid recovery mode n hangs there.can't use volume keys to navigate so i can format it coz its just stuck!
LIVESUIT pack freezes is soon as i plug in the tablet!!!!! HAIMDALL & ODIN can't find the device!!!
am out of options.....if someone knows the solution to this problem then PLEASE HELP ME.
thanx in advance
rusman_id said:
was trying to install CWM RECOVERY on my A13 tablet n now i think its BRICKED!!!
every time i turn it on it goes back to the stupid recovery mode n hangs there.can't use volume keys to navigate so i can format it coz its just stuck!
LIVESUIT pack freezes is soon as i plug in the tablet!!!!! HAIMDALL & ODIN can't find the device!!!
am out of options.....if someone knows the solution to this problem then PLEASE HELP ME.
thanx in advance
Click to expand...
Click to collapse
i have the same problem too with my A13 device when i tried to upgrade the CMW, i installed wrong CMW, i forgot to look for the partition. and now i can't boot in bootloader using ADB, i also can't use fastboot... i try to flash with livesuit but only 3% in flashing and not continued. i hope somebody help to this problem.. thanks in advance..
generic a13 tablet jb 4.2.2 cwm boot loop
i have a zeepad 7.0 (generic a13 allwinner) I have managed to root it. when trying to install cwm 6.0.2.8 I get cwm boot loop. I followed instructions to the T. used correct version for my device. but still seem to get boot loop with can't load cache errors. is there any way to fix this issue. or another way I can install custom rom without cwm? it is already running jb 4.2.2 just looking for a rom with improvements.
gonzo2fast69 said:
i have a zeepad 7.0 (generic a13 allwinner) I have managed to root it. when trying to install cwm 6.0.2.8 I get cwm boot loop. I followed instructions to the T. used correct version for my device. but still seem to get boot loop with can't load cache errors. is there any way to fix this issue. or another way I can install custom rom without cwm? it is already running jb 4.2.2 just looking for a rom with improvements.
Click to expand...
Click to collapse
What you are describing is basically the same flawed procedure I found myself in initially.
DO NOT INSTALL ANY NEW CWM FROM A CWM FLASH LIKE IN OTHER ANDROID DEVICES!!!
99% of the time it does not work and deletes your partition information and messes up your tablet. The ONLY way to rescue it is to find the ORIGINAL ROM for your tablet (or one that is compatible). This will take LOTS of trial and error if you can't find the exact one and have to try to install other A13 tablet ROMS through LiveSuit
LIVESUIT IS THE ONLY WAY TO UPDATE ROMS ON A10/A13 DEVICES NOT THROUGH CWM LIKE OTHER ANDROID PHONES!
HERE is the firmware and instructions for flashing your Zeepad 7.0 back to the stock ROM.
The hardest part is to get it into the FLASH MODE - which when activated, NOTHING will come up on the screen but it will be recognised by LiveSuit.
To get into FLASH MODE:
FIRST - load the ROM into LIVESUIT and get to the bit where it asks about connecting into FLASH MODE
Turn the tablet off/press the reset button on the back with a pointed object
Immediately HOLD the VOLUME + (If any boot screen shows up then you have to start again)
Whilst holding the VOLUME +, plug in the USB cable and then HOLD the POWER KEY
Now let go of the POWER KEY for a second then PRESS IT QUICKLY 10 TIMES
Livesuit should now disappear on the PC and a dialog box will come up about doing a full or normal format (For CWM corruption it is best to do a FULL)
Livesuit will disappear to the taskbar so click it and see if it is flashing. If there is an 0x164 (i think but not sure that is the exact one) error then that means that the ROM WAS INCORRECT (even though you may say you have gotten it from the manufacturers website and it is meant to be the correct one - You have to basically find another that works)
IF THE VERSION OF LIVESUIT DOESN'T RESULT IN A SUCCESSFUL FLASH THEN TRY ANOTHER! THERE ARE ABOUT 3 VERSIONS AND PROBABLY MORE - v1.07, v1.09, v1.11. SOME VERSIONS HAVE SOME ISSUES BUT MAY BE MORE SUITABLE FOR YOUR TABLET. THE MOST STABLE SEEMS TO BE V1.09 BUT TRY THEM ALL TO SEE WHICH ONE WORKS OR NOT.
I hope that helps and if you are really stuck then I recommend you join TechKnow forums as they are way more helpful and specialised than XDA for A13 tablets.
thanks for the advice. I can install stock firmware no problem just looking for something better.
Ah..well then forget CyanogenMod as it not officially supported for this tablet and thus things won't be working 100%. The 2 main ROMs that most people are using for A13 are CookedROM & FaaastJB.
I can recommend both, perhaps FaaastJB has more features but CookedROM is better supported as the creator is one of the mods on TechKnow and gets back to u about ur problems within a day or two with detailed advice. The only issue with these is that the touchscreen drivers don't work out of the vox and u need to patch ones specific to ur tablet to make it work. Sometimes the TS does work but it may be offset or inverted so u have to play around with editing config files out of specific patches with tools provided. In my experience, I had 2 apparent exact ta let's but only 1 would work with any TS patch. The other never worked no matter what I tried, from creating my own patches to extracting drivers from the stock ROM & editing manually - a big learnjng curve and if u have no technical knowledge if how computer languages work then everything will look like gobbledygook and be very time consuming. I preferred the look of Faaast JB but of wouldn't install right so I had to stick with cookedrom in 1 tablet and a stock ROM that I nodded slightly for the other as it wouldn take anything else. These tablets can be really troublesome!
I recommended u install Uberizer as its a huge toolbox of useful stuff for ur A13 and it is recommended to backup ur working stock ROM using it before trying any modifications. U should also get a printout/screen grab of the working ROMs drivers in order to know what TS patches u need for the custom ROMs.there is a world of information on TechKnow forums about this..I can't really help more than this since I do not own an A13 tablet anymore.
D0MINO said:
Ah..well then forget CyanogenMod as it not officially supported for this tablet and thus things won't be working 100%. The 2 main ROMs that most people are using for A13 are CookedROM & FaaastJB.
I can recommend both, perhaps FaaastJB has more features but CookedROM is better supported as the creator is one of the mods on TechKnow and gets back to u about ur problems within a day or two with detailed advice. The only issue with these is that the touchscreen drivers don't work out of the vox and u need to patch ones specific to ur tablet to make it work. Sometimes the TS does work but it may be offset or inverted so u have to play around with editing config files out of specific patches with tools provided. In my experience, I had 2 apparent exact ta let's but only 1 would work with any TS patch. The other never worked no matter what I tried, from creating my own patches to extracting drivers from the stock ROM & editing manually - a big learnjng curve and if u have no technical knowledge if how computer languages work then everything will look like gobbledygook and be very time consuming. I preferred the look of Faaast JB but of wouldn't install right so I had to stick with cookedrom in 1 tablet and a stock ROM that I nodded slightly for the other as it wouldn take anything else. These tablets can be really troublesome!
I recommended u install Uberizer as its a huge toolbox of useful stuff for ur A13 and it is recommended to backup ur working stock ROM using it before trying any modifications. U should also get a printout/screen grab of the working ROMs drivers in order to know what TS patches u need for the custom ROMs.there is a world of information on TechKnow forums about this..I can't really help more than this since I do not own an A13 tablet anymore.
Click to expand...
Click to collapse
I have the stock rom and can flash it back no problem. I have tried all versions of faaastjb but could not get it to install through livesuit. keep getting error message upgrade fails 0x162. I don't know what that means. I will try cooked rom and see if any luck. as far messing with rom drivers I have no clue in that department. guess its time to learn if I want to keep messing with these tablets lol.
gonzo2fast69 said:
I have the stock rom and can flash it back no problem. I have tried all versions of faaastjb but could not get it to install through livesuit. keep getting error message upgrade fails 0x162. I don't know what that means. I will try cooked rom and see if any luck. as far messing with rom drivers I have no clue in that department. guess its time to learn if I want to keep messing with these tablets lol.
Click to expand...
Click to collapse
0x162 means that the ROM is not compatible with your tablet and will never flash. It may flash using other versions of Livesuit or even with the 'only try in a last case scenario' Phoenixcard software..but I have (fortunately) never had to use that. Despite the A13 tablets being 'unbrickable', I read that Phoenixcard CAN brick ur phone although I came across people who had tried it after Livesuit fails and had no problems.
If FaaastJB doesn't work then I highly recommend CookedROM. If that doesn't work then I have no idea what to suggest except Phoenixcard - if you are prepared to accept the risk that it may get bricked. You could also try a search on TechKnow for your particular tablet, post under the FaaastJB/CookedROM posts or create a new thread in the forums (but I think you will get a similar response to this).
D0MINO said:
0x162 means that the ROM is not compatible with your tablet and will never flash. It may flash using other versions of Livesuit or even with the 'only try in a last case scenario' Phoenixcard software..but I have (fortunately) never had to use that. Despite the A13 tablets being 'unbrickable', I read that Phoenixcard CAN brick ur phone although I came across people who had tried it after Livesuit fails and had no problems.
If FaaastJB doesn't work then I highly recommend CookedROM. If that doesn't work then I have no idea what to suggest except Phoenixcard - if you are prepared to accept the risk that it may get bricked. You could also try a search on TechKnow for your particular tablet, post under the FaaastJB/CookedROM posts or create a new thread in the forums (but I think you will get a similar response to this).
Click to expand...
Click to collapse
i have tried every program and only img file that will work is the stock img. guess that's all that's meant to be for it. oh well that's what I get for getting cheap tablets get what you pay for.
i had same problem with my ampe a85 (alwinner a13) .i used livesuit..it was sucess...it will not work if u have used any softwre for rooting like kingo one click root.so try on another system,it will not work on windows 8 too.
gonzo2fast69 said:
i have tried every program and only img file that will work is the stock img. guess that's all that's meant to be for it. oh well that's what I get for getting cheap tablets get what you pay for.
Click to expand...
Click to collapse
Yes unfortunately these tablets are designed with many different configurations by different companies so finding a ROM that matches can prove hit and miss. You may even have 2 of the same tablet bought at the same time from the same company and only one of them works with a ROM or particular touchscreen driver and the other doesn't. I had this problem and could not solve it despite getting the actual hardware configuration from the Android system itself. As you say, you get what you pay for with these tablets.
when you flash a incorrect recovery it will load an incorrect kernel. doing a cat /proc/partitions from the recovery you can notice the kernel see a different partition layout.
on mine original kernel has nanda to nandj so 10 partitions.
the incorrect recovery show nanda to nandg.
when you exit from recovery the recovery executable write somewhere to make a clean boot, but it write it on a wrong partition, so this is cause the bootloop
to recover the situation one has to find a working recovery for the device and the correct number of the ORIGINAL PARTITIONS from here (http://forum.xda-developers.com/showthread.php?t=2189640) then overwrite the bad recovery using dd
1st) start an adb shell and find what is the recovery partition as the bad kernel see it, recovery partition usually is 32mb
my bad recovery seen the recovery partition as nande (while i knew my original recovery was on nandg)
2nd) adb push the correct recovery on the / (adb push recovery.img /)
3th) from the adb shell, dd if=/recovery.img of=/dev/block/nande
4th) reboot
it will start again on the recovery, but this time with the correct partition layout, when you choose reboot it will restart as usual.
Hi I Also have this issue on my tablet
trying to use this thread http://forum.xda-developers.com/showthread.php?t=2189640 to install cwm I ended up having CWM Bootloop mine's also allwinner a13b running 4.2.2 JB, will I be able to fix this using the Faastjb rom? but its only working on A13 and not for A13b??
shutt1e said:
when you flash a incorrect recovery it will load an incorrect kernel. doing a cat /proc/partitions from the recovery you can notice the kernel see a different partition layout.
on mine original kernel has nanda to nandj so 10 partitions.
the incorrect recovery show nanda to nandg.
when you exit from recovery the recovery executable write somewhere to make a clean boot, but it write it on a wrong partition, so this is cause the bootloop
to recover the situation one has to find a working recovery for the device and the correct number of the ORIGINAL PARTITIONS from here (http://forum.xda-developers.com/showthread.php?t=2189640) then overwrite the bad recovery using dd
1st) start an adb shell and find what is the recovery partition as the bad kernel see it, recovery partition usually is 32mb
my bad recovery seen the recovery partition as nande (while i knew my original recovery was on nandg)
2nd) adb push the correct recovery on the / (adb push recovery.img /)
3th) from the adb shell, dd if=/recovery.img of=/dev/block/nande
4th) reboot
it will start again on the recovery, but this time with the correct partition layout, when you choose reboot it will restart as usual.
Click to expand...
Click to collapse
Sir will this work with an allwinner a13b processor with 10partitions, running jb 4.2.2??
NotthedroidIwaslookingfor said:
Hi Android experts!
I need some assistance fixing a problem I caused & am now stuck in a recovery boot loop.
- bought a Thomson QM734-8G tablet (Allwinner A13b clone), running Jellybean 4.2.2;
- PC interface worked fine in MTP and large storage modes;
- setup Android SDK & Java JDK on PC and communicate with tablet via ADB;
All OK so far
After a couple of days, I decided to replace stock recovery with ClockworkMod Recovery, so I could start messing about with the tablet.
I found the CWM 6.0.2.8 mod supposed to work with these tablets and, following instructions, determined it was indeed running on sun5i hardware and had 10 partitions (nandj) and downloaded the appropriate version.
I used ADB sideload to install CWM and everything appeared to work OK ... until I rebooted and found myself stuck in a never-ending cycle of CWM-based recovery bootloop
All I get is the CWM recovery console, with a few lines of error & the tablet will go no further.
E:can't mount /cache/recovery/command
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
Also, pretty much none of the CWM functions work properly and nothing will mount through the 'Mounts and Storage' section, although sideload mode still seems to work.
Attempts to use ADB sideload to install a different CWM or other recovery image have all failed, and LiveSuit and PhoenixSuit both have issues detecting the tablet (despite trying various versions of each & following instructions precisely), so I can't flash a replacement ROM to fix things.
At the moment, I just want to rip CWM out and go back to factory recovery mode and have a working tablet again!
Any suggestions on how to resolve this problem would be greatly appreciated
P.S. I think the Bootloader is locked and the tablet is unrooted. Superuser or SuperSU don't want to install properly. However, using ADB, it looks like I can get root access in shell (#).
Click to expand...
Click to collapse
same problem with
ubislate 7c+
no solutions
i try lots of from here but nothing..........
aasifnasim said:
same problem with
ubislate 7c+
no solutions
i try lots of from here but nothing..........
Click to expand...
Click to collapse
ive modded cwm recovery for the a13 10 partitions just tested on my tablet works find all partitions mount and no boot loop if any one wants it let me know icould probably mod the other partitions but would need a rom dump to do it
Hey guys,
If you want to end the bootloop, the only solution is to flash it with a working rom.
now for the reason of this bootloop:
i hope you all are using cwm 6.0.*.*... Just download the zip according to your partitions and hardware.
Then from your running android device copy the nand.ko file.
it can be found in modules folder
then extract the downloaded cwm zip file adn then the recovery.img and go to the system folder and replace the nand.ko file with yours.
then install the recovery using adb and bingo you're done!
Background
I've got a SGS2 from a friend that is stuck on the Samsung logo (the one after the boot logo, with the swirl/pulse logo). I cannot get into recovery nor download mode with the volume up (down) + home + power key combination but I do get into download mode with a USB JIG. I am certain that the phone was pure stock and fairly certain that it had Android 4.1.2 on it before I got it.
I followed the
[GUIDE] Fix an unflashable or soft bricked GSII. I used the I9100XWLSD firmware, but I remained stuck on the Samsung logo. I also flashed the Kernel (nothing changed) and the Bootloader (+ Kernel + Firmware again) as mentioned in the thread above, but still nothing changed, i.e. stuck on logo, no recovery or download mode via key combo.
Last thing I tried is the Siyah S2-v6.0beta5 Kernel as mentioned here. Now I am stuck on a 'Android gets updated, Apps are opened' screen.
Questions
What else can I try?
Ideally I would like to get access to the internal memory, because there is still stuff on there that was not backuped. What that still be possible?
If I would get it back to run I would like to put CM11 on it.
Thanks!
dapperdanman said:
Background
I've got a SGS2 from a friend that is stuck on the Samsung logo (the one after the boot logo, with the swirl/pulse logo). I cannot get into recovery nor download mode with the volume up (down) + home + power key combination but I do get into download mode with a USB JIG. I am certain that the phone was pure stock and fairly certain that it had Android 4.1.2 on it before I got it.
I followed the
[GUIDE] Fix an unflashable or soft bricked GSII. I used the I9100XWLSD firmware, but I remained stuck on the Samsung logo. I also flashed the Kernel (nothing changed) and the Bootloader (+ Kernel + Firmware again) as mentioned in the thread above, but still nothing changed, i.e. stuck on logo, no recovery or download mode via key combo.
Last thing I tried is the Siyah S2-v6.0beta5 Kernel as mentioned here. Now I am stuck on a 'Android gets updated, Apps are opened' screen.
Questions
What else can I try?
Ideally I would like to get access to the internal memory, because there is still stuff on there that was not backuped. What that still be possible?
If I would get it back to run I would like to put CM11 on it.
Thanks!
Click to expand...
Click to collapse
Did you hold the button combinations when your phone is off for more than 4 seconds? If you flash a kitkat kernel that is newer and doesn't support jellybean (I know this sounds crazy, but just listen), your phone should automatically boot into the recovery after being unable to boot into the rom. Have you done a factory reset and wipe the cache partition yet? Do that in the recovery and flash the jelly bean kernel again.
gsstudios said:
Did you hold the button combinations when your phone is off for more than 4 seconds?
Click to expand...
Click to collapse
Yes, I almost got blisters on my fingers, thats how often (and long) I tried it. Also released the power button but continued to hold vol-up+menu as soon as the boot screen showed up.
If you flash a kitkat kernel that is newer and doesn't support jellybean (I know this sounds crazy, but just listen), your phone should automatically boot into the recovery after being unable to boot into the rom.
Click to expand...
Click to collapse
Does sound a little crazy indeed, but it also makes sense to add such a feature (i.e. boot into recovery if rom isn't present). Any particular suggestion for a KitKat kernel or should I just pick one of those mentioned here?
Have you done a factory reset and wipe the cache partition yet? Do that in the recovery and flash the jelly bean kernel again.
Click to expand...
Click to collapse
Nope, no recovery, ergo no factory reset (or is there another way with a softbricked phone?)
Anyway, that would delete the userdata from the phone as well (e.g. photos), correct? Or are they already gone due to my rom flashing etc.? Oh wait, there is this difference between internal memory and internal usb storage, right?
Update
So I could not decide which one of Kitkat Kernels mentioned here to take. But I tried flashing the CWM recovery files, both GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar and CWM-KitKatCompatible-i9100.tar, with Odin. Flashing went fine, but on boot I only see the bootlogo and then the screen went black.
Any suggestion on what other kernel I could try would be welcome.
dapperdanman said:
Background
I've got a SGS2 from a friend that is stuck on the Samsung logo (the one after the boot logo, with the swirl/pulse logo). I cannot get into recovery nor download mode with the volume up (down) + home + power key combination but I do get into download mode with a USB JIG. I am certain that the phone was pure stock and fairly certain that it had Android 4.1.2 on it before I got it.
I followed the
[GUIDE] Fix an unflashable or soft bricked GSII. I used the I9100XWLSD firmware, but I remained stuck on the Samsung logo. I also flashed the Kernel (nothing changed) and the Bootloader (+ Kernel + Firmware again) as mentioned in the thread above, but still nothing changed, i.e. stuck on logo, no recovery or download mode via key combo.
Last thing I tried is the Siyah S2-v6.0beta5 Kernel as mentioned here. Now I am stuck on a 'Android gets updated, Apps are opened' screen.
Questions
What else can I try?
Ideally I would like to get access to the internal memory, because there is still stuff on there that was not backuped. What that still be possible?
If I would get it back to run I would like to put CM11 on it.
Thanks!
Click to expand...
Click to collapse
The guide which you used for flashing the kernel was for GB and ICS. Now as you have stated your friend's phone is running on JB.
I think you have not rooted your phone correctly but if you have done so try going into download mode thru Usb Jig and install the latest cwm recovery and flash a custom rom (don't flash cm11 directly)
summerchild said:
The guide which you used for flashing the kernel was for GB and ICS. Now as you have stated your friend's phone is running on JB.
I think you have not rooted your phone correctly but if you have done so try going into download mode thru Usb Jig and install the latest cwm recovery and flash a custom rom (don't flash cm11 directly)
Click to expand...
Click to collapse
Yes, I realized that I probably used the wrong kernel from the guide, but AFAIK the I9100XWLSD firmware also contains a kernel, so that should not be a problem (i.e. the kernel was flashed again when I flashed the firmware). I did try the CWM recovery (see my edit above), but to no avail, since I does not take me into recovery mode either. (I assume that you mean that I should flash CM11 from the CWM, not through Odin).
dapperdanman said:
Yes, I realized that I probably used the wrong kernel from the guide, but AFAIK the I9100XWLSD firmware also contains a kernel, so that should not be a problem (i.e. the kernel was flashed again when I flashed the firmware). I did try the CWM recovery (see my edit above), but to no avail, since I does not take me into recovery mode either. (I assume that you mean that I should flash km from the CWM, not through Odin).
Click to expand...
Click to collapse
Did you do backup of your stock ROM. If you can revert to the Samsung logo where you were stuck earlier (boot animation) I think then I can help you
summerchild said:
Did you do backup of your stock ROM. If you can revert to the Samsung logo where you were stuck earlier (boot animation) I think then I can help you
Click to expand...
Click to collapse
I don't have a backup of the original ROM, but I can flash a stock ROM and that still gets stuck on the animated Samsung logo.
Anybody else with an idea?