Related
How do I revert back after one-click root to the stock everything including radio, rom, build, etc. I am currently running Cynagon mod RC1 7 and have had numerous issues, I would just like a clean, simple cut answer so I can give this to someone for the holidays, any help would be mightly appreciated, as i've asked this in the past and can never seem to get a clear cut answer, thanks.
wierd165 said:
How do I revert back after one-click root to the stock everything including radio, rom, build, etc. I am currently running Cynagon mod RC1 7 and have had numerous issues, I would just like a clean, simple cut answer so I can give this to someone for the holidays, any help would be mightly appreciated, as i've asked this in the past and can never seem to get a clear cut answer, thanks.
Click to expand...
Click to collapse
Just flash a full rom, it should restore the radio, the recovery, and the OS. Then do a reset to factory defaults if you are paranoid.
Get the proper rom for you phone here:
http://forum.xda-developers.com/showthread.php?t=1063664
If you're on T-Mobile, you have an i9020-T, this should work for you. It is the full 2.3.6 image.
http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip
Is this also working if you're coming from stock unrooted ICS 4.0.3 ?
And
Is there any risk of loosing IMEI if you're going full ROM ?
mahanddeem said:
Is this also working if you're coming from stock unrooted ICS 4.0.3 ?
And
Is there any risk of loosing IMEI if you're going full ROM ?
Click to expand...
Click to collapse
I have reverted back from 4.0.3 yesterday by reflashing the full 2.3.6 rom without any issues. I'm not sure I understand what you mean by losing IMEI.
My phone works just fine after doing this (more than once!).
pcbroch said:
Just flash a full rom, it should restore the radio, the recovery, and the OS. Then do a reset to factory defaults if you are paranoid.
Get the proper rom for you phone here:
http://forum.xda-developers.com/showthread.php?t=1063664
If you're on T-Mobile, you have an i9020-T, this should work for you. It is the full 2.3.6 image.
http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip
Click to expand...
Click to collapse
Ok here's my problem i did the ics update earlier before you told me this and still having issues, now when I go to recovery I get a android with his chest open with a red caution sign on it...how could I just format everything, essentially make it the way it was out of box so I could start over...because of all the issues I'm currently having.
When you get to that point, you need to hold down power then press vol up. Then you will be able to flash the zip. You need to put the zip on the phone first though, unless you have CWM recovery, in which case you can mount the sdcard section and move it across then, and flash it after.
OK thanks...Just please let's summarize this
1.You were on I9020T bone stock , unrooted
2.You had GB 2.3.6
3.You updated manually (or OTA) to 4.0.3
4.You decided to revert to GB 2.3.6
5.You used exactly the same method of manual update (stock recovery after copying the .zip file and in this case the full ROM of 2.3.6 to SD)
6.You followed the stock recovery steps and chose the .zip 2.3.6..
7.After everything was setup , you booted into GB 2.3.6 without any problems
Is that right ? or better if you make the exact detailed steps you did to revert to GB 2.3.6 would be apreciated
Thanks
furiannn said:
When you get to that point, you need to hold down power then press vol up. Then you will be able to flash the zip. You need to put the zip on the phone first though, unless you have CWM recovery, in which case you can mount the sdcard section and move it across then, and flash it after.
Click to expand...
Click to collapse
Tried, but then I get this error:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: !less_than_int(1316544229. getprop("ro.build.date.utc"))
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Any help?
I think u need a custom recovery to be able to revert back to gingerbread
Sent from my Nexus S using XDA App
Raver27 said:
I think u need a custom recovery to be able to revert back to gingerbread
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
how would I go about flashing the custom recovery? I tried to flash another full rom package with the recovery in it and like i said i got that error...
Do you have a folder in windows where you have been flashing stuff from, using fastboot?
If so, just get this recovery image http://forum.xda-developers.com/showthread.php?t=988686
Download either the blue or green 5023 image. Doesnt matter which just changes colour of mod place the file in the same folder as the fastboot.
Next, with the phone off and after attaching the phone to USB, turn it on while pressing vol-up and power. You should see the boot option screen, the fastboot screen. Leave the phone there.
Now go back to cmd window in windows, and browse to the folder where you have all the fastboot files and where you have put the above image file. Then type in the following:
fastboot flash recovery <image name.img> (without the < >)
press enter and it'll flash the recovery and then you can install the old version of android
furiannn said:
Do you have a folder in windows where you have been flashing stuff from, using fastboot?
If so, just get this recovery image http://forum.xda-developers.com/showthread.php?t=988686
Download either the blue or green 5023 image. Doesnt matter which just changes colour of mod place the file in the same folder as the fastboot.
Next, with the phone off and after attaching the phone to USB, turn it on while pressing vol-up and power. You should see the boot option screen, the fastboot screen. Leave the phone there.
Now go back to cmd window in windows, and browse to the folder where you have all the fastboot files and where you have put the above image file. Then type in the following:
fastboot flash recovery <image name.img> (without the < >)
press enter and it'll flash the recovery and then you can install the old version of android
Click to expand...
Click to collapse
I don't believe I have a folder as such, being a person who is not familiar with the lingo, etc of all this i rooted it with one-click mod, and just flash things through this, are you saying I can flash things externally? sorry to sound like a bum, but i'm trying to understand thanks.
No problem, we're all noobs once, hell i still am and only just coming to terms with it all! Just need to do a bit of researching, but heres the basics...
fastboot lets you flash stuff to the phone from windows, when the phone is attached to the USB and is in fastboot mode (just turned on, from vol-up/pwr).
Can unlock the boot loader and flash recovery images from there. Once thats done, most other stuff can be done from within the new recovery mode, clockworkmod being the one that everyone uses.
over at nexusshacks it's explained really well how to root your phone. And he provides a zip with everything you could want. That zip is the folder I was talking about in the last post. It comes with drivers to install when you first plug the USB in and the PC recognises the phone. Download the pack, install them drivers and then go back to my last post and take it from there
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootnew.zip
EDIT: Also do a full wipe/data reset just before you flash the new rom
furiannn said:
No problem, we're all noobs once, hell i still am and only just coming to terms with it all! Just need to do a bit of researching, but heres the basics...
fastboot lets you flash stuff to the phone from windows, when the phone is attached to the USB and is in fastboot mode (just turned on, from vol-up/pwr).
Can unlock the boot loader and flash recovery images from there. Once thats done, most other stuff can be done from within the new recovery mode, clockworkmod being the one that everyone uses.
over at nexusshacks it's explained really well how to root your phone. And he provides a zip with everything you could want. That zip is the folder I was talking about in the last post. It comes with drivers to install when you first plug the USB in and the PC recognises the phone. Download the pack, install them drivers and then go back to my last post and take it from there
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootnew.zip
EDIT: Also do a full wipe/data reset just before you flash the new rom
Click to expand...
Click to collapse
I'm using clockwork right now, but it seems to be corrupted, im running 4.0.3 right now on a full rom package, so your saying I should still do this? I think i may have done all that before, as the phone is rooted, but I used the one-click method instead.
Just download that file and then you'll have what you need on your pc to do what i mentioned above. Plug the phone in and reflash the new recovery which will not harm it, and then you'll be able to stick gingerbread or ICS back on. You gotta try things out otherwise you'll not understand what is going on. I dont know of any one click thing that will let you go back to default as it was before. After it flashes the new recovery, scroll down to "recovery" on the screen and press the power button, dont restart the system.
In hindsight, while the one click methods are easy to use, theyre getting used by people that dont do the necessary research to learn about the rooting and flashing process. This means you end up skipping so much that you learn about the whole rooting and flashing proocess when doing it manually, which in turn means you have more trouble getting out of it if you want it back to the way it was! No offence intended here, but you just need to man up and do it! All will be well
I have been searching for hours..and still couldn't find an asnwer..
at first when my phone was still alright I did a factory reset and after that
it stuck on a boot screen with android in the middle...for a long time
then I use vol down + power method to reset it and clean everything (like system,cache and boot) all of them...
now I stuck on the green htc boot screen
I tried to install rom and kernel but still won't work I wonder whats the problem now
any idea???
thanks
nias9527 said:
I have been searching for hours..and still couldn't find an asnwer..
at first when my phone was still alright I did a factory reset and after that
it stuck on a boot screen with android in the middle...for a long time
then I use vol down + power method to reset it and clean everything (like system,cache and boot) all of them...
now I stuck on the green htc boot screen
I tried to install rom and kernel but still won't work I wonder whats the problem now
any idea???
thanks
Click to expand...
Click to collapse
You haven't searched that bad, if not you would have come across this:
http://forum.xda-developers.com/showthread.php?t=1396229
Anyway, are you rooted? if you are rooted and did a factory reset then you don't have a Rom in your phone and that is why you are stuck on the splash screen. You even wiped everything, so probably erased usb debugging drivers from the device.
Well, you have these choices: 1) If you still can access your custom recovery (CWM or 4EXT) then you need to put a rom in your sdcard and flash it. You will have your phone back. You can even restore a nand backup and have your system as it was at that time.
2) If you are S-OFF, but can not access a custom recovery, then flash it again and follow option 1)
3) Use a PD98IMG.zip file to flash a RUU in hboot and you will get back. In the link I provided above, you have several links to those files.
In all cases, you will need an sdcard reader or someway to get the files to your sdcard.
Hope it helps....
thanks!!!!
problem solved
I'm having the same problem stuck on the android boot screen I can access recovery and tried to flash a few different roms but with the same results.
Fortis4Eva said:
I'm having the same problem stuck on the android boot screen I can access recovery and tried to flash a few different roms but with the same results.
Click to expand...
Click to collapse
Did you read the link that glevitan posted a couple posts above yours? Did you try what it says? Which option? What happened?
Hi, i did have my phone root some time and everything was perfect, but i tried to install some updates and it did go wrong. I couldnt get into recovery mode anymore, i could install recovery img. and no errors, but when trying to enter recovery the screen is white with green htc logo. I then installed stock ICS and the phone works okey, the HBOOT (volume down and power on) says unlocked and S-OFF, but i cant enter recovery mode and i have installed recovery img from fastboot and with HTC One X software, but no luck. When trying to start clockworkmod i get error that some su folders dont exist, thats why i want to go into recovery to install su-2.3.6.3xxxxx BUT I CANT, HELP! Is it possible to install su from the HBOOT, it search for some PG58xx.img files when entering, can i trick the phone to install su with renaming it to that?
So when u goto su it says u have no root? Have u tried to install 4ext? Or try adb to recovery
try step #2 from this thread (only step #2)
With EXT4 i was able to get into recovery again, thanx. I had tried CWM5.8.4.0 and TWRP 2.1.7 without any luck. I then installed the SU from recovery, now the error about directory didnt exist in Clockworkmod is gone, BUT i still get error like "An error occurred while attempting to run privileged commands!"
Solved. I had to install su binary 3.1.1
Revolutionary ran but small problems
I followed the directions on how to root my Sensation by using Revolutionary. I also installed the ClockworkMod when asked at the end of the Revolutionary process. My present situation is this: According to Revolutionary (when I load it up again) I am already S-Off...what are you trying to do message appears. After that I tried to install Set CPU but it said it could not get the correct permissions (I also installed superuser but don't now how to add permissions, I think it would ask automatically if I was properly rooted). I checked the root status with Root Check basic and it said NO.
Lastly, if I try to start the phone up in fasboot mode (power button/volume down depressed nothing happens until I release both and it goes into a regular Android boot mode. If I go into Revolutionary and do the clockwordmod installation again and ask the phone to reboot into fasboot it works...but when I shut the phone down and try to get in fasboot mode.....doesn't happen.
My phone works fine otherwise.
Any ideas anyone?
Thank you.
Martian59 said:
I followed the directions on how to root my Sensation by using Revolutionary. I also installed the ClockworkMod when asked at the end of the Revolutionary process. My present situation is this: According to Revolutionary (when I load it up again) I am already S-Off...what are you trying to do message appears. After that I tried to install Set CPU but it said it could not get the correct permissions (I also installed superuser but don't now how to add permissions, I think it would ask automatically if I was properly rooted). I checked the root status with Root Check basic and it said NO.
Lastly, if I try to start the phone up in fasboot mode (power button/volume down depressed nothing happens until I release both and it goes into a regular Android boot mode. If I go into Revolutionary and do the clockwordmod installation again and ask the phone to reboot into fasboot it works...but when I shut the phone down and try to get in fasboot mode.....doesn't happen.
My phone works fine otherwise.
Any ideas anyone?
Thank you.
Click to expand...
Click to collapse
you are getting completely confused with SOFF and root to device
understand the terms
here read the below guide
Android Terms
now the clockworkmod you have isa custom recovery ..it wont root your device
now to go to bootloader/fastboot using power + volume down buttons ..you need to first uncheck fastboot from settings->power
one you go to bootloader ..you go to recovery from there (that is cwm ..and you need to flash a root zip file )
then you will have root on the phone
EDIT: SOFF means security off ..once you gain that ..you can change the recovery to a custom one ..also you can flash custom roms ...
ganeshp said:
you are getting completely confused with SOFF and root to device
understand the terms
here read the below guide
Android Terms
now the clockworkmod you have isa custom recovery ..it wont root your device
now to go to bootloader/fastboot using power + volume down buttons ..you need to first uncheck fastboot from settings->power
one you go to bootloader ..you go to recovery from there (that is cwm ..and you need to flash a root zip file )
then you will have root on the phone
EDIT: SOFF means security off ..once you gain that ..you can change the recovery to a custom one ..also you can flash custom roms ...
Click to expand...
Click to collapse
Insted to uncheck fastboot, take out the battery (and the charger), insert the battery, vol down + power on.
root zip file is the same as SU.something(3.1.1)binary.zip, correct?
Rooted
I fiddled with the phone a little more last night and determined that I might not have had a good install of superuser. I downloaded a different file from a different source, installed it and a different file for CWM and voila...I have root. I still don't have the ability to go into fastboot by holding the power button and volume down button at boot up. The screen just remains black and when I let go of the buttons, it vibrates and goes into the standard boot up.
Also, is anyone using Set CPU on this phone? I guess I have to disable Perflock or something....is it ok to disable this?
Thanks all for your responses.
Martian59 said:
I still don't have the ability to go into fastboot by holding the power button and volume down button at boot up. The screen just remains black and when I let go of the buttons, it vibrates and goes into the standard boot up.
Click to expand...
Click to collapse
You have to put the phone realy off first. Remove the charger, takeoutthe battery and then insert the bat. and try voldown+poweron. OR uncheck the fastboot option in the settings.
Both worked
buffelen said:
You have to put the phone realy off first. Remove the charger, takeoutthe battery and then insert the bat. and try voldown+poweron. OR uncheck the fastboot option in the settings.
Click to expand...
Click to collapse
You are 100% correct, thank you. Taking out the battery worked and so did turning off the fastboot option on the power menu in settings.
Thanks so much guys. It's nice to know you can submit a problem on a comment board and people will give you straight answers without making counterproductive comments.
One more subject....Is it OK to disable Perflock so SET CPU or ANUTU CPU controller can correctly recognize the CPU frequencies? And do these programs provide beneficial processing power and/or extended battery life? Any maximum setting recommended for overclocking?
Thanks again!
Hello, I've recently completed the Bootloader unlocking method with Easy Ace Root Tool. Bootloader is unlocked and SHIP S-ON, I need to flash a rom. These roms require S-OFF and have no method to flash them with only an unlocked bootloader and S-ON.
So let me get this straight, us 'low level' and unexperienced users are left without any method to gain S-OFF privileges without following the vague guide provided at tau(dot)shadowchild(dot)nl/attn1/?p=411 Yeah... I can't.
Trying to find alternate methods I have only gone in circles and keep running into old how-to guides. The more I read the more confused I become. I hope someone can point me in the right direction, I would really appreciate it!
Thanks,
Ninjewbag
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
bananagranola said:
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
Click to expand...
Click to collapse
Good deal, thanks for the reply!
I put the ROM Android Revolution HD 9.0 on the root of my SD card, booted in recovery mode and chose the recovery option, I got the red exclamation mark icon so I pressed VOL up + power button which didn't work so I pulled the battery. I tried all above steps again but this time I was able to successfully get into "Android system recovery <3e> with VOL up + power button. With 4 options:
Reboot system now
Apply update from sdcard
wipe data/factory reset
wipe cache partition
I chose the option to wipe all data, said it could not find Efolder name)'s and "data wipe completed successfully".
Then I wiped cache, then chose the option to apply update from sdcard, it said "Invalid operation" then "success rebooting by reason 00" and proceeded to reboot by itself.
Phone factory reset, I rebooted into recovery again with the same red exclamation mark error. Pressed Vol up + power and back into "Android system recovery". At the bottom in yellow text it says "E: Can't open /cache/recovery/command". I tried another "update from SD card" and recieved error: "success rebooting by reason 00" and reboots.
I don't have a nandroid backup as I read I needed Root to make one, but the phone still works fine as far as I can tell. I don't have a working simcard in it though.
Also from what I've read my eMMC chip may be fried so it looks like I'm retiring early. I'll keep an eye on this thread among others with the same problems.
Cheers,
Ninjewbag
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
RadRacer said:
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
Click to expand...
Click to collapse
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
http://forum.xda-developers.com/showthread.php?p=31211732
ninjewbag said:
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
Click to expand...
Click to collapse
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
turboyoshi said:
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
Click to expand...
Click to collapse
Thanks for the reply but as for installing the 4ext free updater version, it wasn't on the market so I used android injector to place and install that APK. None of the options worked as they all give the same error "it seems your phone is not rooted, this option will not function" etc.
RadRacer said:
http://forum.xda-developers.com/showthread.php?p=31211732
Click to expand...
Click to collapse
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
ninjewbag said:
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
Click to expand...
Click to collapse
Glad to help. Wanna hit thanks?
Hi all,
I thought it be good to warn all Alcatel Pixi 4 (4) owners. The current version of the stock rom of the 4034N, which is sold here in the NL has what I think is a terrible bug.
If you enable unlocking in the development options, go to the fastboot, all it takes is to unlock the flash and your phone will get stuck in the boot animation.
I tried to recover by formatting /data (/data is destroyed as could be expected to protect the userdata), but it does not solve the problem.
Flashing a custom ROM like CM13 solves this problem, but I bet this is the reason why I see so many calls on the Internet for Stock ROMs for the 4034N. Have not found a good stock ROM for it and also Alcatels Mobile Upgrade site does not seems to support the 4034N (probably still one software version for it, so no upgrade required yet?).
So better know what you are doing when messing with this phone.
Anybody got the same experience (I can confirm that this was tested by me and my friends with three different Pixi 4's)...
Best regards,
Peter
Good news!
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
I think I'm seeing the same problem with a 4034X (UK variant, as sold by Tesco Mobile). Unfortunately, the mobile update software isn't working for me as it's detecting that I've already got the latest version of the ROM installed already and won't let me install it again. AIUI, the CM13 system has a few issues, so I'd rather not go that root, so would still like a stock ROM if at all possible. Anyone have any pointers?
Hmm. Have managed to get beyond the resetting user data boot loop with the following procedure:
* boot to recovery (power + vol up)
* from recovery menu, choose "boot to bootloader"
* at bootloader, connect via USB to PC
* run "fastboot -w"
* run "fastboot boot <filename for twrp recovery image>"
* at twrp recovery menu, run the standard "wipe" options
* reboot
Haven't yet finished booting, but it's gone to the standard boot animation, which I never succeeded in getting to before.
Update: 8 minutes and counting into the boot process. Doesn't look like it's going to work.
One question worth asking: does this mean that *all* operations that cause a factory reset on an affected 4034 cause a boot loop? Or is it only unlocking the boot loader?
I managed to soft brick my 4034X simply by allowing my email program to encrypt the device. The encryption apparently failed and now it's stuck on boot animation. As @jh3141 said, the Acatel upgrade tool doesn't work. I guess I need to find a stock ROM, but my Googling hasn't found one yet. Can anyone help?
palbeda said:
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
Click to expand...
Click to collapse
Same here with a 4034D - got my phone back alive and still a unlocked bootloader. rooted it, works great.
Thanks!! :good:
i need help
Tampopo said:
Same here with a 4034D - got my phone back alive and still a unlocked bootloader. rooted it, works great.
Thanks!! :good:
Click to expand...
Click to collapse
Can you brake this down for me? am kind of new to all this but i really need to root my device
jh3141 said:
Hmm. Have managed to get beyond the resetting user data boot loop with the following procedure:
* boot to recovery (power + vol up)
* from recovery menu, choose "boot to bootloader"
* at bootloader, connect via USB to PC
* run "fastboot -w"
* run "fastboot boot <filename for twrp recovery image>"
* at twrp recovery menu, run the standard "wipe" options
* reboot
Haven't yet finished booting, but it's gone to the standard boot animation, which I never succeeded in getting to before.
Update: 8 minutes and counting into the boot process. Doesn't look like it's going to work.
Click to expand...
Click to collapse
Any luck with the UK version 4034X?
I'm stuck in the booting process just like you were.
me too - Pixi 4(4) chaos on unlocking.
Absolutely the same experience here.
I have nuked 2 of these trying to unlock. It is a brilliant phone, but this is a painful feature - as you describe.
My history is in one of the threads on this site. - I agree, I would love a stock ROM for it.
palbeda said:
Hi all,
I thought it be good to warn all Alcatel Pixi 4 (4) owners. The current version of the stock rom of the 4034N, which is sold here in the NL has what I think is a terrible bug.
If you enable unlocking in the development options, go to the fastboot, all it takes is to unlock the flash and your phone will get stuck in the boot animation.
I tried to recover by formatting /data (/data is destroyed as could be expected to protect the userdata), but it does not solve the problem.
Flashing a custom ROM like CM13 solves this problem, but I bet this is the reason why I see so many calls on the Internet for Stock ROMs for the 4034N. Have not found a good stock ROM for it and also Alcatels Mobile Upgrade site does not seems to support the 4034N (probably still one software version for it, so no upgrade required yet?).
So better know what you are doing when messing with this phone.
Anybody got the same experience (I can confirm that this was tested by me and my friends with three different Pixi 4's)...
Best regards,
Peter
Click to expand...
Click to collapse
I also softbricked my 4034X after unlocking the bootloader and couldn't get the phone to boot into recovery or the bootloader. I eventually managed to flash a stock ROM with SP Flashtool as described here https://www.getdroidtips.com/install-official-stock-rom-on-alcatel-pixi-4-4/ - this restored the ability to boot into recovery or bootloader but the ROM wouldn't boot so I couldn't enable developer settings to allow OEM unlocking. I then tried flashing the ROM for the dual-SIM version of the 4034X (risky!) and this booted and I was able to unlock the bootloader and flash TWRP recovery. The next problem was when & flashed CM13 and got an error message saying that TWRP couldn't access /data. It then got stuck in a recovery bootloop. Next I used TWRP to format all the partitions but it still couldn't access /data and broke the ability of the Mobile Upgrade Tool to read the phone. My next step is to try flashing a different custom recovery but I'm rapidly losing the will to live and would be very interested in any suggestions.
UPDATE - got it sorted by re-flashing the dual-SIM 4034X ROM (even though I have the single SIM version!), flashing ctr-6.6-4034 recovery, doing a normal wipe then formatting the /data partition then flashed CM13. I guess the data partition must have got corrupted.
I have exactly the same problem with pixi 4 4043f. I unlocked bootloader and then flashed following your instructions on that link you shared. But I see is a white screen frozen no options shown just booting voice behind.... I have flashed it several times but same results I still cant entry fastboot or recovery... Volume down + power or volume up + power dn take me anywhere just that frozen white screen with booting ring tone in the back and thats it... Kindly guide me
i had a similar problem, but i always wanted to flash cm13, so i was fine.
There is an amazing thread here for our device.
For those of you with the 4034X, i have ported cm13 to it specifically, bu there are too many bugs, but if anyone wants it, just tell me!
also, can i just say, softbrick if you oem lock aswell :,(
i wanted to test something, but after fastboot oem lock, and then fastboot reboot, i get an android being repaired? key combo's not working, adb/fastboot not responding, can't remember how i fixed it when i oem unlocked ...
edit-
got into recovery with key combo, now it's just to fix it!
Can any of you guys with the 4034N try this method of rooting? Without unlocking the bootloader?
Masgisk Rooting
kirito9 said:
Can any of you guys with the 4034N try this method of rooting? Without unlocking the bootloader?
Masgisk Rooting
Click to expand...
Click to collapse
For reference: I tried this on a stock 4034X and it failed (couldn't persuade it to boot the custom recovery without going through the full unlock process). Fortunately, there are now copies of the stock ROM available for download (e.g. https://androidfrog.com/a3nr9) so with any luck I won't need to go back to the dodgy CM13 port that constantly runs out of memory and soft-reboots...
Update: I've installed the stock ROM I linked to above, and it seems to be working pretty well. Only issue was that the scatter file that came with it was apparently broken. Fortunately, one that I had hanging around from attempts to fix this problem last time seemed to work with it. I've attached that to this message in case anyone else needs it.
jh3141 said:
For reference: I tried this on a stock 4034X and it failed (couldn't persuade it to boot the custom recovery without going through the full unlock process). Fortunately, there are now copies of the stock ROM available for download (e.g. https://androidfrog.com/a3nr9) so with any luck I won't need to go back to the dodgy CM13 port that constantly runs out of memory and soft-reboots...
Click to expand...
Click to collapse
Thanks, I'll be sure to add a notice for 4034X users in the Magisk guide. I have yet to see a stable CM13 ROM for MT6580 with 3.18.19 kernel. There seems to be an issue with this device chip and ROMs.
Finally got root on the Pixi4-4034
Hi everyone,
yeah I finally managed to root the alcatel Pixi 4-4 (4034) (3G MODEL). It was really tricky and there are quite some issues you have to deal with.
Therefore please read carefully my instructions and remember I am not responsible for any inconvenience, do it at your own risk.
First of all you have to unlock the bootloader and here comes the first problem. On the Pixi4 this operation leads to a sotfbick because the unlocking process deletes completely the data-partition. The phone can't boot anymore and ends in a bootloop.
To resolve this problem you must reflash the phone with SP-Flash-Tool. After reflashing the bootloader remains unlocked so that you should be able to continue with the rooting process. The second problem is that I could find only one working ROM for flashing. It is for the 4034X, my phone was a 4034D (dual SIM), after flashing I had an 4034X what means that my Pixi became a single-SIM phone, I can live with that.
Here are the necessary steps to obtain root on the Pixi4
1. UNLOCKING BOOTLOADER
- Go to settings -> about phone -> hit many times on "build number" till developer message appears
- Enable "OEM unlocking" located in developer options.
- Switch also "USB debugging" on
- Open the command prompt window (cmd)
- Connect the phone to the PC
- Boot into fastboot-mode by typing "adb reboot bootloader"
- Confirm the debug authorization window on the phone, check "always allow from this computer" (afterwards phone should boot into fastboot, otherwise retype the command above)
- Unlock bootloader by typing "fastboot oem unlock"
WARNING: this deletes the data-partition leading in a softbrick and bootloop,
you have to reflash the phone afterwards to continue rooting!
- Confirm the unlocking with the volume-up key
2. REFLASHING THE PHONE
- I found only this working firmware for the 4034X on this page like described by jh3141:
https://forum.xda-developers.com/android/general/warning-current-pixi-4-4-4034n-t3463154/page2
- You have also to use the scatter file described by jh3141
- After loading the scatter-file in SP-Flash-Tool you have to link the missing img-files in the SP-Flash-Tool-Window
- If you flash the 4034X firmware over an 4034D you will end in a single-SIM phone instead of a dual-SIM.
- After flashing the phone will boot again so that you can continue with flashing the twrp-img.
3. ROOTING THE PHONE
- To root the phone you have to install the twrp-image, the one for the Pixi 4034 you find it here:
https://forum.xda-developers.com/showpost.php?p=68049551&postcount=97
- Download and untar the file at the bottom of the page: twrp-3.1.0-0-4034.tar
- Open the command prompt window (cmd)
- Connect the phone to the PC
- Boot into fastboot-mode by typing "adb reboot bootloader"
- Flash twrp by typing "fastboot flash recovery twrp-3.1.0-0-4034.img"
- Download Super-SU "SR1-SuperSU-v2.78-SR1-20160915123031.zip" from
https://download.chainfire.eu/1003/SuperSU/
and put the zip-file on the phone (external or internal storage)
- With the phone switched off boot into twrp by holding power and volume-up keys togehter
- In twrp go to "Advanced" -> "Terminal" -> Type the following code:
echo "SYSTEMLESS=true" > /data/.supersu
- Go back and choose "Install" -> flash the Super-Su-file (SR1-SuperSU-v2.78-SR1-20160915123031.zip)
- Reboot and you’re done, you have root and super-su on the PIXI4
- If you want to uninstall system-apps proceed to the next step.
4. UNINSTALLING BLOADWARE APPS
- You can’t uninstall system-apps directly from the Android-OS,
if you delete the apps with some uninstall-tools it’s strange but the phone will reinstall them after a reboot.
- To succeed you must uninstall the apps in twrp
- Be careful, uninstalling the wrong apps will end in a bootloop or bootfreeze and you will have to reflash the phone starting at step 2.
- Boot into twrp -> go to "Mount" -> check "System" -> go back and choose "Advanced" -> "File Manager"
- In file-manager navigate to the appropriate app-folders and delete the .apk-files
- IMPORTANT: before rebooting you have to wipe the dalvik-cache
- Go to "Wipe" -> "Advanced Wipe" -> CHECK ONLY "Dalvik / ART Cache"
- Confirm wipe and reboot
I personally like the Pixi4-4034, it’s a very small one that is very useful as second phone especially on holidays .
Have fun.
i bricked my alcatel
i have an alcatel pixi 4 (4) 4034x and when i unlocked the bootloader it softbricked my alcatel, the only solution i did was relflash it using spflashtools
same problem
palbeda said:
I found out that there is a global site from Alcatel where you can find an update of Alcatels Mobile_Upgrade_S_4.5.9 which DOES support the 4043N.
The good news is not only that this software can bring your phone back to stock ROM, but also that if your Flash is unlocked before you recover, it is still unlocked after the recovery. So rooting is very simple then. Cost me 2 minutes to do it:
adb boot recovery.img (you can boot the twrp bootimage from ADB, no need to flash it) and then directly install the superuser.zip
Presto!
Click to expand...
Click to collapse
I have exactly the same problem. But I haven't been able to find this Mobile_Upgrade_S_4.5.9. Any help will be greatly appreciated,
thnx,
Herman
update: i found the mobile upgrade tool. But it says the latest firmware is already installed. Earlier i tried spft, flashing seemed to go well but the phone stays in animation/bootloop.
Can anybody help?