i tried to put custom rom on sns but i decided to just keep it stock i want to put the original recovery that it came with so i can update in the future is it possible to update even if the bootloader is unlocked?
problem:i flashed an image but couldnt use adb with my pc.
is there a image where i can just use fastboot to flash without using adb? i was using a recovery that required me to use adb to erase some kind of sh? was stuck on that. so if theres a recovery thats doesnt need to use adb? i have a recovery but i cant flash a rom.
Are you still rooted ?
It is rooted.
If you are on stock rom already, then you can do a search using root explorer or like adao file manager for install-recovery and find it and return its name to install-recovery.sh I assume this is what you changed previously ALTHOUGH if you have CWM installed then you can probably ( and easier...ly ) just find the stock image of your phone and flash it. I just did this this morning to my phone actually..
the image for i9020T can be found here http://forum.xda-developers.com/showthread.php?t=1062777&highlight=stock+i9020t
some quick searching can probably find some other images for the different models.
once you flash one of those you may have to use fastboot to lock the bootloader back up.
"fastboot oem lock" command when connected to your phones bootloader
ive flash the zip but everything is still the same ive tried to flash with cwm v2.5.1.8 i thinks somehow this version of cwm doesnt work because i cant flash anything with this i also tried to look for install recovery.sh on adao file explorer but couldnt find it. if you can help me out would be very appreciated.
Pop out the batter of your device and tell me the model number i902......
What version of clockwork do you have?
you could try to download rom manager from the marketplace and use that to flash clockwork again. once you have done that try flashing the stock img for your model phone.. flashing zips from cwm should work.... although watch your screen when you do it see if it throws any errors
Related
Hi guys,
For the last 2 nights I´ve been trying to get a CG Mod 6.1 on my HTC Magic 32B.
I have rooted it with onclick-root method and tried a bunch of things like ROM Manager and flashing via fastboot (brings up "remote not allow" error). Nothing worked out.
Here are the facts:
HTC Magic with OTA upgrade to 2.2.1
hboot: 1.33.0013
radio: 2.22.28.25
Rooted with Oneclick method
Do I need a goldcard? How do I do that? What hboot Version do I need? What Radio do I need? What do I have to do first?
Are you certain the Root took? Are you seeing the Superuser icon in your app drawer?
When you were using Rom Manager did you flash, or attempt to flash a custom recovery, and if so did it install ok?
What happened when you tried to flash a ROM using Rom Manager?
I'm sure we'll get to the bottom of this
Yes, rooting has worked...Icon is there everything looks fine.
With the Rom Manager i tried to install "update-cm-6.1.0-DS-2708port_S" aswell as the "update-cm-6.1.0-DS-signed". Both did not work.
I still can boot to my standard OTA 2.2.1
Try wiping your phone in recovery and then install the rom
hang on a minute...
it sounds like you haven't installed a custom recovery before trying to flash the rom. Can you clarify...have you actually done this yet?
The process should go root/recovery/nandroid backup/rom in that order.
yeah you re right...i dont have a custom recovery
i just tried to load "recovery-RA-sapphire-v1.7.0G.img" on the console
su
# flash_image recovery /sdcard/recovery.img
does not work, i get: flash_image: not found
USB debugging is enabelde
3rd party software is enabeled
is there another way to get flash the recovery ?
Rom Manager!
At the top you should have the option to flash clockworkmod recovery. Select that; it will run and then the phone should reboot. I usually do it again to confirm. If it installed correctly the first time you'll get a pop up saying that it is installed.
If all goes to plan select 'backup current rom' from within Rom Manager. This is a nandroid backup and can be re-installed from recovery any time you wish to return to stock.
NOW you are free to install a custom ROM of your choice
Post back if you encounter any issues.
I have tried that. It flashes, gives my a popup that it installed correctly.
But it does not reboot.
When i choose restart in recovery mode it boots up the phone an gets stuck on the vodafone logo. BatteryOut reboot and i am back at the good old 2.2.1 OTA
do i have to wait long?!? cant be, right? do i need to hold down any buttons?
If you try the backup option now you'll soon find out if the recovery did indeed install ok. (it won't backup if the recovery isn't installed)
i restarted...flashed the recovery again. got popup confirmation. then chose backup rom and got stuck at the vodafone logo
You must be pretty frustrated by now. It might be time to start asking for more help in the dev section of the Magic forum HERE.
I hope that somebody has the answer!
Thanks for your help...i ll see if someone else has any ideas.
roodee said:
yeah you re right...i dont have a custom recovery
i just tried to load "recovery-RA-sapphire-v1.7.0G.img" on the console
su
# flash_image recovery /sdcard/recovery.img
does not work, i get: flash_image: not found
USB debugging is enabelde
3rd party software is enabeled
is there another way to get flash the recovery ?
Click to expand...
Click to collapse
Are you are aware that the command you need to type will be
flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img
The command points to the exact file name on your sd card so if you just wrote flash_image recovery /sdcard/recovery.img and the recovery file was not called "recovery.img" it would not know what to look for.
I'm not sure if this is what you have or whether you just copied and pasted from a guide, but I just thought I'd put it out there in case that is the case.
Hope this helps.
I tried using superboot to root my nexus s, but ended up with having a stuck google screen upon reboot.
Is there anyway I can recover my phone to the original state. I can get into the boot screen by pressing up volume and the power button and I have downloaded an original rom; however, I don't know how to upload this rom
into the phone.
I unlocked the bootloader, and have the android SDK installed. I do have a response when I use the command "fastboot devices"
Is there any possible way to save my phone? Please help, Thanks in advance
is there a recovery image saved under the recovery option?
Hey I'm having the exact same problem as the OP.
I don't have a recovery image saved in recovery, so I tried to flash the latest CWM recovery image through adb, but the device isn't found.
My phone was rooted, then upgraded to 2.3.4, then got 2.3.6 OTA, but lost root. Tried to root with Superboot and now my phone's stuck.
How can I get my phone to work again?
ri ch said:
Hey I'm having the exact same problem as the OP.
I don't have a recovery image saved in recovery, so I tried to flash the latest CWM recovery image through adb, but the device isn't found.
My phone was rooted, then upgraded to 2.3.4, then got 2.3.6 OTA, but lost root. Tried to root with Superboot and now my phone's stuck.
How can I get my phone to work again?
Click to expand...
Click to collapse
You have to flash CWM using fastboot, not adb.
fastboot flash recovery recovery.img
Once you have the custom recovery flashed you can flash superuser in CWM to get root back or just flash one of the custom ROMs that include superuser.
Yes, I did exactly that.
I really have no idea what I'm doing so I'm extremely grateful for people who do.
Thanks
I am in the same boat as these other chaps. After installing the 2.3.6 OTA update I tried to root with Superboot and now my Nexus S just sits on the Google screen with the open padlock.
I've tried installing CWM recovery, as well as the boot.recovery.img that comes with Superboot, and it seems to install successfully. After rebooting my phone still sits on the Google screen, however.
Am I doing something wrong here (I'd previously rooted with few problems)?
EDIT: I should mention that after flashing the .img I'm trying to boot into recovery - at this point it just sits on the Google screen.
EDIT 2: Never mind, I sorted it. I tried using a different recovery.img (from this thread) and I was then able to get into recovery and restore a backup.
Flashed the NexusBeam ICS rom and deleted the radio and bootloader img that came with the zip and now my phone wont boot at all, I was under the impression by deleting the bootloader.img it just wouldnt install the new bootloader which is what i wanted but it seemed to haved deleted mine in the process
Yup.. Deleting those files from the package would result in the bootloader and radio being wiped and replaced by nothing.. You will probably have to use Odin to flash a stock image. Hopefully someone can help you with that, as I've never used it.
This is precisely the reason I, and some others, were asking devs not to include those files in the rom package..and we were getting crap from other people about "complaining".
Sent from my Nexus S using Tapatalk
PhillyboyDROID said:
Flashed the NexusBeam ICS rom and deleted the radio and bootloader img that came with the zip and now my phone wont boot at all, I was under the impression by deleting the bootloader.img it just wouldnt install the new bootloader which is what i wanted but it seemed to haved deleted mine in the process
Click to expand...
Click to collapse
What phone do you have? to want to delete NexusBeam ICS bootloader? I have nexus s GT-I9020 & was gonna delete the radio, but thaught I would give the new ICS one a try first! (could always flash compatible radio later on!) & it works flawlessly! Then I added GlaDOS 2.4 kernel which changed the boot animation which I didn't like (simple, just deleted bootanimation.zip from system/media, then pulled original bootanimation.zip from NexusBeam zip, & replaced!)
Just dowload NexusBeam again & use cwm recovery or fastboot to reflash NexusBeam & if you want to change radio also, do it at the same time after copying your desired rado to your sd-card & wiping dalvik cache first, then if you change your stock kernel in NexusBeam to dev one, just use method I mentioned previously if you want to change your boot animation to whatever you want! Good luck!!
I cant boot into my bootloader or recovery at all....I can boot into ICS but if i try to but into my recovery from ROM manager my phone just turns off, and if i turn it off it wont turn back on until I run a unbrick program i found. Im stuck after that though, dont know how to flash bootloader without fastboot
PhillyboyDROID said:
I cant boot into my bootloader or recovery at all....I can boot into ICS but if i try to but into my recovery from ROM manager my phone just turns off, and if i turn it off it wont turn back on until I run a unbrick program i found. Im stuck after that though, dont know how to flash bootloader without fastboot
Click to expand...
Click to collapse
After you use unbrick program & get into recovery, use fastboot to flash new cwm recovery.img! (fastboot flash recovery cwm recovery.img!) Then when you're in cwm recovery, mount usb storage & put your newly downloaded NexusBeam.zip on your sd-card & install through cwm recovery!
CrackDaddy said:
After you use unbrick program & get into recovery, use fastboot to flash new cwm recovery.img! Then when you're in cwm recovery, mount usb storage & put your newly downloaded NexusBeam.zip on your sd-card & install through cwm recovery!
Click to expand...
Click to collapse
Fixed it, didnt realized i had to hold power and vol up while running the unbrick process...thanks for all your help guys
PhillyboyDROID said:
Fixed it, didnt realized i had to hold power and vol up while running the unbrick process...thanks for all your help guys
Click to expand...
Click to collapse
Glad to hear you fixed it. Don't delete the radio or bootloader files from the package again. Instead, you can just flash a different radio after flashing the rom. The updated bootloader is a keeper though.
Sent from my Nexus S using Tapatalk
Unlocked and rooted ATT HTC One X and flashed pa_evita-2.54-09NOV2012-210217 ROM.
Boot up as far as an Android character with the lettering Paranoid Android 2.+ and then freezes there.
Any suggestions?? If nothing else, how do I get back to stock ROM?
Noob rldieb
rldieb said:
Unlocked and rooted ATT HTC One X and flashed pa_evita-2.54-09NOV2012-210217 ROM.
Boot up as far as an Android character with the lettering Paranoid Android 2.+ and then freezes there.
Any suggestions?? If nothing else, how do I get back to stock ROM?
Noob rldieb
Click to expand...
Click to collapse
1. What recovery are you using?
2. Did you wipe cache/dalvik-cache, factory reset?
In order to get back to a stock ROM, you will need to boot into recovery, then mount your usb storage. Put the rom on your sd card and then unmount. To be safe, wipe the cache and dalvic cache, then flash the stock rom.
What hboot are you on?
You may have flash boot.img first if you are on hboot 1.14
I think he just didn't full wipe
That's just wrong!
Sent from my Nexus 7 using Tapatalk 2
I'm having the same issue. I'm trying to flash this same rom on a device rooted on 2.20. I think my issue has something to do with flashing the boot.img. I have tried to flash using hasoon's toolkit, which doesnt seem to work, i have extracted the zip and placed the boot.img in the kernel folder, and when the command prompt tries to flash it, it says error. I have also tried flashing the kernel from the phone directly using the flash flash image gui app, and it says flash is successful, but when it prompts to boot into recovery, the command doesnt work from my phone so i have to boot into recovery manually.
can anyone give a solid link or tutorial on how to successfully flash the boot img onto my device, every link I have read uses windows cmd prompt, which when i try to replicate, it never works.. So, for now I flashed back to viper rom, since it has its own installer. It would be so nice if all these other roms were able to install like that.
thanks in advance for the help
threetwentyfizzle said:
I'm having the same issue. I'm trying to flash this same rom on a device rooted on 2.20. I think my issue has something to do with flashing the boot.img. I have tried to flash using hasoon's toolkit, which doesnt seem to work, i have extracted the zip and placed the boot.img in the kernel folder, and when the command prompt tries to flash it, it says error. I have also tried flashing the kernel from the phone directly using the flash flash image gui app, and it says flash is successful, but when it prompts to boot into recovery, the command doesnt work from my phone so i have to boot into recovery manually.
can anyone give a solid link or tutorial on how to successfully flash the boot img onto my device, every link I have read uses windows cmd prompt, which when i try to replicate, it never works.. So, for now I flashed back to viper rom, since it has its own installer. It would be so nice if all these other roms were able to install like that.
thanks in advance for the help
Click to expand...
Click to collapse
I do have a solution! Download Flash Image GUI from the market (it's $1.99) and it will do the process for you, no commands needed! The app is also available via XDA for free, do a search and download it.
Hi.
I am relatively experienced user who has rooted and installed custom roms on samsung galaxy and HTC desire phones before.
I have now attempted to root my alcatel onetouch pixi 4 (4034X) using instructions from this thread :- https://forum.xda-developers.com/android/general/alcatel-one-touch-pixi-4-t3376597
I got as far as flashing twrp recovery and now the phone is stuck in constant reboot. I downloaded alcatels mobile upgrade tool in hopes of reflashing the stock rom but it seems to be looking for a later rom than the one I have installed and keeps telling me I have the lastest and so wont flash.
So can I recover from this at all or have I just bricked my phone? Is there a way to FORCE the mobile upgrade tool to reflash the current rom rather than looking for an upgrade?
It seems that everything except the bootloader is intact so is there another tool I can use to restore the bootloader?
Any help would be greatly appreciated.
Looks like I managed to unbrick using a combination of SP Flash tool and an SPFT rom for the 4034X I found on the internet. will now try reflashing a different recovery tool.
O.K. so I think what is happening is an issue when unlocking the bootloader and not when flashing recovery.
This is what I did:-
1. Enabled developer mode.
2. Turned on usb debugging and unlocked bootloader oem
3. Rebooted phone, plugged in cable and accepted connection authorisation.
4. From windows typed adb reboot bootloader. Went into to fastboot.
5. Typed fastboot oem unlock, Pressed volume up on phone.
At this point I was put back in fastboot but none of the buttons worked and the phone looked like it had frozen. Was It wiping data at this point? There was no indication that it was doing anything.
I removed the battery and reinserted but when I restarted I got the same boot loop problem. Had to restore stock firmware AGAIN.
Am I doing something wrong?
Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?
nyarlathotep_uk said:
Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?
Click to expand...
Click to collapse
Hi & welcome to xda-assist,
you can try to force the installation of supersu systemless by this step, chances are good that this will make it boot properly.
boot into twrp >go to the terminal > and type:
echo SYSTEMLESS=false>>/data/.supersu
Don't know if the recovery you use has this terminal option but it's very likely.
You can do additional a Google search on "force SuperSU systemless" to get more information / background information..
Good luck
Sent from my OnePlus 2 using XDA Labs
Thanks for your reply Sam.
I only read that after I had found a copy of a CM13 Rom that worked with The 4034X. I basically flashed superSU first then did a wipe, then installed the custom rom and google apps nano before downloading the supersu apk from google play and reinstalling. Now I have a rooted phone with a custom rom and am somewhat happier. The reason I wanted to root was to remove the bloatware that was taking up 1.5 GB of my already measly 2GB internal memory and this new ROM only takes up .5 GB.
I still have some pain. For example many of the Rom Toolbox Pro functions don't work and I think its because the system image seems protected and refuses to mount rw no matter what I do. Even issuing a remount command using the device name from cat /proc/mounts tells me the block device is read only. I also seem to be unable to verify if I have busybox or install it due to the same reason.
It also took me some time to work out that the boot animations weren't stored in /data/local or /system/media but to /data/system/theme.
This used to be so much easier in the days of ice cream sandwich and lollipop. Ah well!
Update:- Managed to flash busybox 1.26 using a flashable zip via adb sideload in Caliv Recovery (Caliv can't see my adopted storage for some reason).
I'm happy now! Would still like to have a rw system so I can remove some system apps I don't use but its no biggie.