Ok guys, Heres what I do & what happens,
(model # C6833)
1- root device
2- install new boot kernel (adv-stock-v4) (( Even tried v5))
3- unlock bootlader (only had to do it the first time, bootloader stays unlocked)
4- install cwm/TWiRP
5- get into TWIRP or CWM & wipe as I should
6- install rom. (It wont install)
7- reboot
8- stuck @ sony logo. & then reboots,
9- reinstall stock rom
This happens every time I try to install a rom.
I also get the message before I reboot, no root, would you like cmw/twirp to fix it, I go with yes. & ive tryed no as well. no difference. Still get stuck @ Sony logo & get reboot loop.
Any ideas ?
Im not new at rooting & roming.
Hey, it sounds like you're installing NUT's dual recovery and are trying to flash a CM/AOSP based ROM? I didn't find it possible to flash non-Sony ROMs using that recovery, myself. What you need to do is to first flash the kernel (boot.img) from the ROM you're trying to flash. You can do this using fastboot with the phone set to fastboot mode. The FlashTool program comes with what you need, and there's a guide to using it in the development forum. The kernel contains the recovery (either CWM or TWRP), so after flashing that, you can boot to recovery and install any CM/AOSP ROM you wish.
Triflot said:
Hey, it sounds like you're installing NUT's dual recovery and are trying to flash a CM/AOSP based ROM? I didn't find it possible to flash non-Sony ROMs using that recovery, myself. What you need to do is to first flash the kernel (boot.img) from the ROM you're trying to flash. You can do this using fastboot with the phone set to fastboot mode. The FlashTool program comes with what you need, and there's a guide to using it in the development forum. The kernel contains the recovery (either CWM or TWRP), so after flashing that, you can boot to recovery and install any CM/AOSP ROM you wish.
Click to expand...
Click to collapse
I did the flashtool thing. ( I'll edit my post ) I did the boot.img & Im trying to use SlimRom. Everything seems to be fine until I try & install the rom. Then it goes to hell.
Btw, Slimrom is compatable.
So what's the actual error message you get upon installing a ROM?
Something like, installation canceled. could not install rom. It goes threw a few steps. gets a few things installed (or so it seems) & then it hangs & I get that message. I thought, at first, it may have been a corrupt download. But after a few times of downloading it. I kinda think its no longer that.
Have you tried another ROM? Someone else is also having boot trouble with Slim in its development thread.
No actually, I have not. I will soon though now. And report back. First I need a stock U.S. rom. Just in case. Cant seem to find one.
Been using a CE (Central Europe) based stock rom.
Related
Hi,
Due to HTC's special touches, the recovery image doesnt stay flashed, and on normal boot its flashed over (meaning if i try to go to recovery after a normal boot, i get the red triangle stuff, and have to pull the battery). I was wondering if this would potentially cause troubles if i was trying to flash a custom ROM from recovery? in other notes, i do find sometimes i have to pull the battery 4 or 5 times to get it to normally boot (thats without holding the buttons >.>).
Thanks in advance.
HTC HERO recovery image flashing problems
I am having exactly the same problem!
I did a quite a bit of research on how to root, backup and flash my HERO and every guide I found describes the process using Universal AndRoot + Rom Manager and it seems there should be no problems. I already rooted my phone successfully, installed Rom Manager and flashed either ClockworkMod 2.5.0.1 or RA Recovery 1.7.0.1 which are able to boot but only once. The next time I reboot I get the red triangle warning and it loads into stock recovery (by pressing vol_up + powroff buttons), so the custom recovery lasts only one boot cycle. I was able to backup but I don't want to risk to wipe and flash since there is a chance it might stuck in the bootscreen loop afterwards and I won't be able to do anything.
There is a thing with s-off and SPrecovery which helps to resolve the problem but it doesn't look like there is anything for HERO.
Any help would be appreciated.
ps I tried to manually flash recovery from inside the phone and from windows command line with the same result.
forum.cyanogenmod.com/topic/8182-how-to-root-your-hero
posted some similar comments over there, and the only init script that i can find when in recovery.
Yeah I posted my question there too.
I was able to find some information about the issue (he is talking about Villain ROM but I think it doesn't really matter):
pulser_g2:
Repeat the process again, as I think stock ROMs try and overwrite the recovery each time they boot. When you finish the process, immediately nandroid and flash VR12. That will then flash a new recovery, AmonRA 1.6.2a, and you will be sorted
Click to expand...
Click to collapse
So it looks like we should just go ahead and flash a custom rom which, in theory, will eliminate the problem.
yeah was tempted to just flash, but sending duck my system img for him to dissect anyway.
yeah worked fine, running cm6.1 now
Yeah once you root you have to flash a custom rom before reboot or u loose the root
I learnt it after lots of reboots and re roots.
but now I wanted to know if I could save the original rom which i have as nand backup to make as an update.zip like custom rom for safe keepimg
I flashed CM6.1 -based TastyFroyo 1.2 and I can confirm custom recovery stays flashed now.
Im tired of installing many ROM's and 2 different Recovery, some "cant open .zip" and having boot problems, and in other recovery, it can install roms, but other aslo cant open .zip, and also having boot problems,
Im really tired of reflashing stock ICS Fw then root, install Recovery again, after failing installing ROMs.. its too long to reflash, root, install recovery,, its waste my time and having headache after failing installing ROMs for almost a week
Is there any fast solution or what would you do after you fail installing ROMs and cant boot? even do you can enter recovery? what proper should do next? would you also reflash again stock ICS then root and install recovery?
or any other fast way solution..
Please help
Root and install recovery onto your device. Enter recovery and make a nandroid back up of your device. Flash your new rom and reboot the device. If you boot loop or the rom doesn't work or even if you just don't like it, enter recovery (may have to remove the battery to restart a boot cycle) and use your nandroid back up to restore your device.
Before flashing the new rom, you should make sure that the kernel is compatible with the one that is already on your device. If it isn't compatible, you will also want to flash the new kernel using fastboot/flashtool, and not recovery. Also make sure you have a back up of your rom's current kernel so you can flash the original kernel, if you decide to go backwards.
justmpm said:
Root and install recovery onto your device. Enter recovery and make a nandroid back up of your device. Flash your new rom and reboot the device. If you boot loop or the rom doesn't work or even if you just don't like it, enter recovery (may have to remove the battery to restart a boot cycle) and use your nandroid back up to restore your device.
Before flashing the new rom, you should make sure that the kernel is compatible with the one that is already on your device. If it isn't compatible, you will also want to flash the new kernel using fastboot/flashtool, and not recovery. Also make sure you have a back up of your rom's current kernel so you can flash the original kernel, if you decide to go backwards.
Click to expand...
Click to collapse
Thanks I think that what im looking for.. the Nandriod backup..
gota way to find that now and how to install
Thanks a lot!
Hmmm...the most easiest way it to unlock your bootloader first...then flash custom kernel...this can help you skip rooting and installing recovery again and again if something goes wrong cause all custom kernel is pre-rooted and got recovery by default....
next you need to find which custom roms you want to flash...some custom roms have their own kernel or flash any custom kernel that is compatible with the roms....
remember, custom kernel is important cause if you flash the wrong kernel, you might get bootloop after flashing the roms....
Pusak Gaoq said:
Hmmm...the most easiest way it to unlock your bootloader first...then flash custom kernel...this can help you skip rooting and installing recovery again and again if something goes wrong cause all custom kernel is pre-rooted and got recovery by default....
THANKS! I have a plan now to unlock my BL
thanks for that info
Click to expand...
Click to collapse
I tried following this:
http://forum.xda-developers.com/showthread.php?t=1580070
"INSTRUCTIONS" part:
* RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
* RECOVERY: Install Rom: Download
* RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
* RECOVERY: Wipe Cache Partition
* RECOVERY: Wipe Dalvik Cache
* Reboot and enjoy
Click to expand...
Click to collapse
did all the above, never forgot any of the 3 wipes/resets that were necessary.
used this rom file:
http://goo.im/devs/paranoidandroid/roms/i9100g
(latest one)
for my Galaxy Samsung S II GT-i9100g.
I had CWM and also had a rooted android 2.3.
first boot it showed me the normal samsung boot screen, for 45 minutes....
so I restarted and the phone gave me the same behaviour..
so I removed the battery to turn off the phone, and attempted to reinstall the whole thing, going through this process again from scratch
not forgetting any of the wipes etc...
now every time I boot it, it leads me to CWM instead of the normal boot screen and the expected paranoid rom eventually...
I followed this path because CM 10 failed me because upgrading from 2.3 to 4.x requires going through something that is called "stock" or as I think it actually is - google's /manufacturer's original firmware/rom production line thingy
and after that it needs me to re-enable root on that stock rom all over again. And only then I may attempt to install CM10...
so I picked paranoid instead, because in it's instructions is showed me no such constraint. heck it can't give me that constraint because there is no "stock" of android 3.x for smartphones
but then this issue happened... so I need your help.
I found similar search results but couldn't figure out their solutions or how whatever triggered that same problem (which isn't mentioned in those threads) is related to what I did to my phone... (so that I will not repeat the same mistake)
your help is much appreciated as I need it so so much!
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
gastonw said:
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
Click to expand...
Click to collapse
by "flash"ing you mean the option "install from a zip file" in CWM in recovery mod?
if I have some rom, the only way for me to install another would always be by going through that middle step of also installing a 'stock' rom as well?
there is no way around it?
installing a 'stock' rom, wouldn't it make me loose my root I have on the phone and force me to root it all over again before I can continue install anything at all?
thats the reason I wanted to try out the paranoid way of doing this instead of the CM10, because I have no interest in rooting my already rooted phone and I hoped that paranoid does not need me to go to stock first....
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
some questions
ONE QUICK IMPORTANT QUESTION BEFORE THE REST:
If I use mobile odin, will I be able to use it to install stock rom and also root it at the same time?
SECOND IMPORTANT QUESTION:
you said I could flash whatever I want and still have root, but my problem was not 'not having root', it was not having the flash process complete successfully... how do I attack that?
THIRD IMPORTANT... info... :
My "BUILD" version is "GINGERBREAD.XXKL5", isn't that a 'stock' one?
If you don't have a lot of time,
then the rest of this post is not as important as the 2 questions above...
gastonw said:
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
Click to expand...
Click to collapse
the saddest part is that I couldn't figure out most of what you just said
what is 'nandroid'? 'flashing'? do you mean like dd in linux? copying to the entire flash storage device?
'IMEI'? huh..? O_O
at the moment I was able to 'get back on my feet', I restored everything back to normal with manual copying of important parts of the CWM corrupted backup from this week, and old stuff for a CWM backup made few months ago.
now that I am at a 'normal' state.. I want to install paranoid or CM10 on my GT-I9100g.
which one of those 2 does not force me going through installing stock?
I have this fear of installing stock that it will take away my root and that I will have to use adb from command line to re-enable root afterwards, which I have bad experience with.
I need to know a few things before I attempt to install stock via CWM,
will installing stock disable my root? will installing stock disable my ability to load recovery boot menu CWM?
is 'root' an attribute or state that belongs to the running rom itself after boot has been completed and to that only?
or does it also belong to the state the device is at while in the recovery boot menu CWM ?
I tried messing around with ADB in the past to see if I could root devices via that way but it wasn't very successful so thats why I'm afraid of having to attempt it again.
bumpitybump
even though a year later, I would still love some replies
resurrecting my motivation to do this once again.
copy paste from my other post;
before flashing, you will need these;
-stock rom (get it from Sammobile, sign in and select your country and phone model)
-blazing kernel for recovery (search in XDA)
-custom rom (CM, PA, Supernexus...your choice)
-backup your data
-GApps (get the latest one)
-you must know what are you doing and dont flame/blame other member if something wrong
how to flash;
-make sure you are on latest stock rom (mine is JellyBean 4.1.2), if not like the OP, flash the latest stock rom using Odin;
*reboot your phone in Download Mode
*open Odin and in PDA option select your stock rom and then Start
*if done it will display Done and disconnect your phone, it will boot up
*if bootloop, reboot into Recovery Mode, and then wipe data and cache, and then reboot normally
-after updating your phone to latest stock rom, copy your custom rom, GApps, and Blazing kernel into external SD card, then reboot into Recovery Mode
-choose "apply update from external storage" and choose Blazing kernel, wait for it to finish update
-reboot normally, and then reboot back to Recovery Mode. this time you will notice that your recovery is different from the previous one
-select install zip > choose from external storage/sdcard 1 > and then choose your custom rom. then wait for it to finish update
-repeat the above step to install GApps, and after that reboot normally
-if bootloop, reboot back to Recovery Mode and then wipe data, cache and dalvik and then reboot
-done, now you are running on custom rom
Click to expand...
Click to collapse
and about the root, i believe that almost all custom rom rooted
Hi All,
I am new to the forum and new to rooting. I did loads of reading and thought that I would give rooting a go on my Sony Xperia Z Ultra. After rooting, and doing dual boot install I downloaded Dirty Unicorns 4.4.4 and Gapps. Booted into recovery and flashed the two zip files. After booting up the rom, it keeps crashing and giving a systemui fail / crash message. So I cannot do anything with the rom because the message comes up a second after I close it.
Not only that, there is now no custom recovery on my phone. Has anyone else been in this situation or can anyone please let me know what I can do to either flash a custom recovery?
I have also tried connecting my phone to the Flashtool to flash the stock rom, however as soon as I connect my phone to my pc it boots the system up and doesnt allow me to go into flash / fastboot mode.
Please help!
Thanks,
RJ
Hi,
I will have your thread moved to your device section.
Good luck!
Darth said:
Hi,
I will have your thread moved to your device section.
Good luck!
Click to expand...
Click to collapse
Thanks! Didnt know where to post.
Recovery should be included in the ROM (I've not flashed it though to test)
press the vol. up key just after booting when the LED turns purple should do the trick.
Do you want to load another custom ROM [1] or go back to Stock Sony [2]?
[1] Download custom ROM, flash boot.img in fastboot, flash ROM from recovery with wipes
[2] Download a FTF and flashtool (http://flashtool.net), flash FTF - fully clean Sony system again
RJacobz said:
Hi All,
I am new to the forum and new to rooting. I did loads of reading and thought that I would give rooting a go on my Sony Xperia Z Ultra. After rooting, and doing dual boot install I downloaded Dirty Unicorns 4.4.4 and Gapps. Booted into recovery and flashed the two zip files. After booting up the rom, it keeps crashing and giving a systemui fail / crash message. So I cannot do anything with the rom because the message comes up a second after I close it.
Not only that, there is now no custom recovery on my phone. Has anyone else been in this situation or can anyone please let me know what I can do to either flash a custom recovery?
I have also tried connecting my phone to the Flashtool to flash the stock rom, however as soon as I connect my phone to my pc it boots the system up and doesnt allow me to go into flash / fastboot mode.
Please help!
Thanks,
RJ
Click to expand...
Click to collapse
Can you clarify what you mean by "doing dual boot install", are you referring to the multirom mod or something else.
Did you unlock your bootloader?
Because I see no mention of that and when I flashed scrubbers port of kitkat via twrp it bricked my ultra and I had to buy a new one.......
blueether said:
Recovery should be included in the ROM (I've not flashed it though to test)
press the vol. up key just after booting when the LED turns purple should do the trick.
Do you want to load another custom ROM [1] or go back to Stock Sony [2]?
[1] Download custom ROM, flash boot.img in fastboot, flash ROM from recovery with wipes
[2] Download a FTF and flashtool (http://flashtool.net), flash FTF - fully clean Sony system again
Click to expand...
Click to collapse
Hey how to unlock the bootloader in sony phones and after its unlocked how to go to fastboot mode..
Hi so after updating from the stock zv6 to lollipop update my phone won't install a custom ROM. Every time I try to turn it on it goes straight to TWRP and went I install a ROM or try to load a backup as soon as I hit reboot it goes back to the TWRP page. Amy ideas?
You must flash back, using Flashtool, to zv4, then reroot, then flash newest TWRP. OTA software not included, because they flash every partition of the phone, including the boot loader. Stock roms like zv6 and zv8(lollipop)or AOSP, must be flashed from xda from here on out, because they've been modified to work correctly on zv4 boot loader. TWRP and root access only work correctly with zv4 boot loader.
sent from my LG G3
It sounds like there is no OS installed or it is stuck a reboot-loop. Try pulling the battery out for 10 seconds and if it still goes into twrp you know that it isn't a reboot-loop. When you go to restore a rom and it has the bar that shows the amount of storage does it say "0 MB"? If it does it means that twrp can't mount the storage on the phone thus causing it to not install/reboot. Have you tried side loading a rom via adb? Are you trying to install a rom off of a sdcard? I have seen many issues in the past sdcard related.
If you can please answer the following:
1) What is the message you are getting from twrp (if there is any)?
2) Have you installed a custom kernel and if so witch one?
3) What twrp are you running (the bumped one from xda or from the official twrp site) and what version is it?
4) Have you tried adb and pulling the battery?
If you answer these questions they should be able to tell us all that we need to know in order to help you out.