Related
hello, I'm Spanish so excuse my bad English.
I'm trying to load some rom eclair and no I finished the installation,
error busybox sys,
and all abortions.
I checked the integrity of the downloaded rom.
I have recovery: 1.6.2g. that screenshot is old
here a screenshot of the error:
The following observations were made by me :
1: Wrong Forum
2: Minimal information provided by Original Poster
To assist you i need more information such as your radio/spl and what rom it is you are trying to flash.
Since english isnt your native language, guys dont flame the guy plz.
apology for the location on forum
spl: original htc g1
rom: SuperEclair v8.2 (htcmania) and SuperEclair v3.0 (xda-developers)
Ok i would re-download the rom just to be sure no corruption has occured.
Then i would do a phone wipe.
Then i would backup my information on my sdcard and create an ext partition
Then i would flash this rom.
Daneshm90 said:
Ok i would re-download the rom just to be sure no corruption has occured.
Then i would do a phone wipe.
Then i would backup my information on my sdcard and create an ext partition
Then i would flash this rom.
Click to expand...
Click to collapse
room tested with sha1, correct code, downloaded two times
wipe: all, the five wipe.
sd: partitioned into ext3, swap, fat32 (without deleting content for:fat32 loading rom)
I found this on their thread. Try it
+ boot into recovery
+ Wipe everything (data, dalvik, ext, batt stats, rotation)
+ partition sd (96/128 swap, 512/1024/whatever you want, rest fat)
+ repair ext
+ ext2 to ext 3
+ ext 3 to ext4
+ Put rom sd (toggle MS)
+ wipe data and dalvik again
+ flash zip from sd
+ reboot system
Click to expand...
Click to collapse
Daneshm90 said:
Ok i would re-download the rom just to be sure no corruption has occured.
Then i would do a phone wipe.
Then i would backup my information on my sdcard and create an ext partition
Then i would flash this rom.
Click to expand...
Click to collapse
Daneshm90 said:
I found this on their thread. Try it
Click to expand...
Click to collapse
now I do.
question:
repairing ext. that achievement? returns since ext3 to ext2?
ext repairing fixes any file access issues u get from switching roms. Just do as it says.
Daneshm90 said:
ext repairing fixes any file access issues u get from switching roms. Just do as it says.
Click to expand...
Click to collapse
Indeed the steps!.
error screenshot:
K that error i remember seeing when i had the wrong spl. So it seems as though you need danger spl for his rom or you could use firerat's patches to make it work on stock spl
Daneshm90 said:
K that error i remember seeing when i had the wrong spl. So it seems as though you need danger spl for his rom or you could use firerat's patches to make it work on stock spl
Click to expand...
Click to collapse
I would like to retain the original spl. by the break.
Ok try this.
Flash the rom, when u get the error flash again. Dont reboot or do anything just flash again.
I just flashed on my phone with stock spl and it worked.
So its something wrong with urs.
Daneshm90 said:
Ok try this.
Flash the rom, when u get the error flash again. Dont reboot or do anything just flash again.
Click to expand...
Click to collapse
hise what I intended.
update the rom, error.
new charge, without rebooting. and error. :S
elfasito said:
hise what I intended.
update the rom, error.
new charge, without rebooting. and error. :S
Click to expand...
Click to collapse
Are you sure you are downloading it without any corruptions because it sounds like you are downloading bad files left and right??? I just re downloaded and flashed and worked fine...
You need EXT 4 for some reason but that isn't the problem when your flashing your missing files try re downloading in a new browser like Firefox or Opera
Somthing like this happened to me one time after flasing an eclair rom. I couldn't restore nandroid ("error: try running nandroid from adb" blah blah), and if i wiped and flashed it wouldn't get past splash screen. I finally flashed super d OVER an eclair rom, booted up, did sign it, went back to recovery, wiped and reflashed super d, and viola. I think my errors were like his, too.
Edit: HOWEVER! I could reflash the eclair rom and it boot up perfectly. I didn't try a different ROM. So I can't really say if another eclair would have done the same thing.
One more edit: This actually happens to me everytime i flash an eclair rom then try and go back to a donut. that's why i just stay away from them. really like them, just scared one day it wont be fixable.
XxKOLOHExX said:
Are you sure you are downloading it without any corruptions because it sounds like you are downloading bad files left and right??? I just re downloaded and flashed and worked fine...
You need EXT 4 for some reason but that isn't the problem when your flashing your missing files try re downloading in a new browser like Firefox or Opera
Click to expand...
Click to collapse
I assure you that is not corrupt.
and I tried to load 2 different rom.
and also have tested the code with sha1.
if you have time, adjuntame the rom that was downloaded.
use firefox
r3s-rt said:
Somthing like this happened to me one time after flasing an eclair rom. I couldn't restore nandroid ("error: try running nandroid from adb" blah blah), and if i wiped and flashed it wouldn't get past splash screen. I finally flashed super d OVER an eclair rom, booted up, did sign it, went back to recovery, wiped and reflashed super d, and viola. I think my errors were like his, too.
Edit: HOWEVER! I could reflash the eclair rom and it boot up perfectly. I didn't try a different ROM. So I can't really say if another eclair would have done the same thing.
One more edit: This actually happens to me everytime i flash an eclair rom then try and go back to a donut. that's why i just stay away from them. really like them, just scared one day it wont be fixable.
Click to expand...
Click to collapse
I do not understand much, (English)
you could spend the steps or explain a little better?, I would appreciate
edit:I never flash an eclair.
single donut
without error flash this rom: http://forum.xda-developers.com/showthread.php?t=633957
the others give error
I rooted my phone and flashed 4ext recovery.I have a 8 gb SD card with a 512 ext4 partition.
I made a nandroid backup and started flashing roms....I tried to flash a 3.5 sense ROM..success ...everything went fine.....but after restarting my phone it gets stuck on HTC boot screen....I tried to flash another rom but same results....It gets stuck in HTC boot screen or it simply reboots into recovery........What I am doing wrong??...
....
After many times of flashing roms my phone booted successfully.....but if I reboot it will get stuck on HTC boot screen and then it will reboot in recovery mode........PLS HELP ME GUYS...!!
I forgot to mention that I tried to restore my original rom but it says md5 sum mismatch....
U don't know that u will stuck on boootanimation again...wipe cache,dalvik cache should solve problem.
~Swaypovano sa Desire S BRE!~
Adidas108 said:
U don't know that u will stuck on boootanimation again...wipe cache,dalvik cache should solve problem.
~Swaypovano sa Desire S BRE!~
Click to expand...
Click to collapse
I make a full wipe .before I flash a ROM ....I tried this with no results.....
Which version did you have before flashing to ext4? You could have made a mistake following the procedure, maybe skiped a step???
This should have been a very safe procedure, yet there are no guarantees...
My advice to you is to follow the procedure all over again, trying to put your phone ina phase you have begun with.
LogicXLz' said:
Which version did you have before flashing to ext4? You could have made a mistake following the procedure, maybe skiped a step???
This should have been a very safe procedure, yet there are no guarantees...
My advice to you is to follow the procedure all over again, trying to put your phone ina phase you have begun with.
Click to expand...
Click to collapse
I don't think I did something wrong here........I s offed and flashed cwm recovery via revolutionary..After that I flashed 4ext recovery then I made a nandroid backup and started flashing roms.......But thanks for your advice!
Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.
Do I have to factory reset in recovery and does factory reset result in Bootloop,
Do I have to Superwipe.
Or do this individually:
Format/wipe data
Wipe cache
Wipe dalvik cache in advance(menu)
Format SD ext, system, boot, in mounts and storage.
What do you wan't to do with the phone, factory reset from menu will get you to bootloop for sure, doing it from recovery...... it's 50/50. But why do you want to do this?
If you want to change the rom, then just follow the instructions for it, so please do tell, what is your goal.
I just rooted my phone today this is first time I'm installing a Custom Rom.
There is an Instruction in the Rom I want to install. Do factory reset (While in Recovery I think.)
Just flash superwipe first, after that, the rom and something else if needed, if you are going for sense4, manually wipe everything from recovery, except the sd.
And that's it,......... uuu one more thing, backup your messages with some app, if you have important ones.
Thanks for the info!
Yeah I'm going with sense4.
Last question what is the minimum memory card size in doing the partition, I have a 4GB Micro SD is that enough?
Personally I haven't tried sense 4 (neither of them), but from what I read, you need at least 1GB ext3 or ext4(if I'm wrong somebody to correct me). And that's it. If you don't know how to make a partition check out my signature, there should be tutorial about that.
So what is the Custom Rom your using maybe I'll use that.
I'm on aokp (by legen_dary), but that's irrelevant, if you like sense, give it a try, sense roms are cool, they are just not my cup of beer. And whatever you choose to install, should be something that you like, anyway installation process for 95% of roms(sense or no sense) is pretty much the same, so if sense got your atention, go for it!
Ok thanks man you really made my day!
+1 to whatever shortyoko said upto now.. And one more point to be added iz that use yannou's recovery ( r recovery in jaggy jaggs tutorial) for flashing sense roms as they mount sd ext while flashing properly.. Other recoveries have some issues.. Though I tried with twrp to flash build 6.. And it worked..
I'm on my tab
Thank you for that Red Devil!
Stuck in a bootloop
I searched a lot on the forum tried going back to the stock ROM, but still stuck in bootloop need help
Details buddy, details. Also in my signature are two versions of stock rom, check them out
Hello, i think i ran into a major problem with my one sv(k2_ul android 4.2.2).
Well it all started when i was in the recovery(twrp 2.7.0.1), i got distracted by someone at school and tapped around on the screen.
Apparantly i wiped it.
Then at home i tried to restore my backup i made after i rooted it, but it ´didnt, work because:
a.) twrp was unable to mount the sdcard
b.) twrp was unable to mount int_sd
after some research i found out that while wiping, the filesystem might got screwed up. I tried several things to fix it like mounting the phone as an usb devices and reformatting it to fat32 --> didnt work, because it wouldnt even recognise the phone.
Also tried wiping it with adb shell, didnt work either.
Tried flashing different recoverys, but twrp 2.7.0.1 seems to be the only one working for me(all other recoverys i tried didnt even start)
Well thats my problem, as mentioned above i have a backup of data, boot and system partitions and also have a stock rom.
Hope someone can help me?
king3sebi said:
Hello, i think i ran into a major problem with my one sv(k2_ul android 4.2.2).
Well it all started when i was in the recovery(twrp 2.7.0.1), i got distracted by someone at school and tapped around on the screen.
Apparantly i wiped it.
Then at home i tried to restore my backup i made after i rooted it, but it ´didnt, work because:
a.) twrp was unable to mount the sdcard
b.) twrp was unable to mount int_sd
after some research i found out that while wiping, the filesystem might got screwed up. I tried several things to fix it like mounting the phone as an usb devices and reformatting it to fat32 --> didnt work, because it wouldnt even recognise the phone.
Also tried wiping it with adb shell, didnt work either.
Tried flashing different recoverys, but twrp 2.7.0.1 seems to be the only one working for me(all other recoverys i tried didnt even start)
Well thats my problem, as mentioned above i have a backup of data, boot and system partitions and also have a stock rom.
Hope someone can help me?
Click to expand...
Click to collapse
Are you S-Off and have you tried taking everything back to stock ?
[GUIDE] Back to Stock ICS for k2u & k2ul with S-Off - old.splatterhand
http://forum.xda-developers.com/showthread.php?t=2386426
Sorry if I m off.. Im trying to learn and help out also.
rb2tfm said:
Are you S-Off and have you tried taking everything back to stock ?
[GUIDE] Back to Stock ICS for k2u & k2ul with S-Off - old.splatterhand
http://forum.xda-developers.com/showthread.php?t=2386426
Sorry if I m off.. Im trying to learn and help out also.
Click to expand...
Click to collapse
im not s off, how would i do that and what does it do?
EDIT: After some research i found out that i cant go s off with my device in the current state
Wiping whit TWRP doesn't work?
And I don't no if you can boot whit an other file system as ext4
kreumadragon said:
Wiping whit TWRP doesn't work?
And I don't no if you can boot whit an other file system as ext4
Click to expand...
Click to collapse
It wont even mount the internal storage or sd so wiping is impossible