Shortly after getting the phone I rooted and installed CM / Synergy ROM. I'm not entirely sure what happened but a few days after I started receiving a message about insufficient storage when attempting to update apps on the Market. So I figured just redoing everything would be a good way to resolve the issue.. that went well.
I followed the how to root your vzw guide. I wiped and reset back to factory, flashed the Synergy ROM again with Odin, and then applied the latest Imoseyon LeanKernel. I then spent hours getting everything set back up thinking the phone was fine. After the phones first reboot I had a message stating the phone was running an unauthorized version of software and I should contact Verizon. So I panicked and went back to the guide following the section titled 'How to get back to stock from any rom' I applied both of the VRAL files as it says and then the stock ROM.
Not sure if I'm just compeltely confused on part of the process here or what, but I do not understand why I still have a 'custom' boot screen showing, and now am stuck in a boot loop. Although, I'm no longer seeing the scary contact Verizon message.
I had also run into something after hours of digging called root66. So I tried that as well and I'm still stuck in the same position. The custom counter has gone up each time I've flashed.
Vol up + home + power enter the screen saying it's loading custom boot and then the phone vibrates / restarts / hangs in boot.
Help is greatly appreciated!
jacksheadache said:
Shortly after getting the phone I rooted and installed CM / Synergy ROM. I'm not entirely sure what happened but a few days after I started receiving a message about insufficient storage when attempting to update apps on the Market. So I figured just redoing everything would be a good way to resolve the issue.. that went well.
I followed the how to root your vzw guide. I wiped and reset back to factory, flashed the Synergy ROM again with Odin, and then applied the latest Imoseyon LeanKernel. I then spent hours getting everything set back up thinking the phone was fine. After the phones first reboot I had a message stating the phone was running an unauthorized version of software and I should contact Verizon. So I panicked and went back to the guide following the section titled 'How to get back to stock from any rom' I applied both of the VRAL files as it says and then the stock ROM.
Not sure if I'm just compeltely confused on part of the process here or what, but I do not understand why I still have a 'custom' boot screen showing, and now am stuck in a boot loop. Although, I'm no longer seeing the scary contact Verizon message.
I had also run into something after hours of digging called root66. So I tried that as well and I'm still stuck in the same position. The custom counter has gone up each time I've flashed.
Vol up + home + power enter the screen saying it's loading custom boot and then the phone vibrates / restarts / hangs in boot.
Help is greatly appreciated!
Click to expand...
Click to collapse
Maybe odin again,if you can get into adb?
in adb type in
Code:
adb reboot download
this should get you into odin mode
If that doesn't work try
Code:
adb reboot recovery
here's an example of how output should look
Code:
Erics-MacBook-Pro:applications eric$ adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
if you do this you this properly you should be in recovery clockwork mod, wipe everything or restore to a previous rom, i hope that helps.
http://goo.im/devs/invisiblek/i535/stock.kernel.tar here's the stock kernel
Odin back to stock rom, odin stock kernel, boot into recovery, wipe data factory reset. Next time read the guide more thoroughly and unlock your bootloader before flashing.
ericerk; adb is not detecting the device. I'm receiving the following message when trying to list devices or using the reboot commands you have recommended; "List of devices attached" and nothing after. Also "error: device not found" Odin is detecting the device.
droidstyle; Those are the steps I followed. The problem is I can not enter into the recovery menu now. When I hold Vol up + Home + Power while the device is booting it attempts to load, vibrates the device, and then hangs in a boot loop. I had also downloaded EZ and unlocked the bootloader before hand. Maybe the mistake I made was to lock it after everything was done? Maybe I misunderstood something I had read about doing so to avoid a push and causing the exact issue I have?
Thanks again!
Why did you relock the bootloader? That was a big mistake!! Now you need to follow section 2...flsh a stock rom and kernel, boot into stock recovery, wipe data, reboot. This time Unlock the bootloader and leave it unlocked!
Just for verification/clarification, the stock rom and kernel I have downloaded are;
Samsung-Updates.com-GT-I8530_XEF_1_20120614154832_nv1pfwdaeb / I8530XXLF3_I8530OXXLF1_HOME.tar.md5
Samsung-Updates.com-SCH-I535-VZW-I535VRALF2_Kernel / kernel.tar
I may have misread something. I read to avoid getting a push from Verizon and possibly locking out the device that the boot loader needed to be locked.
Doing as you've recommended now. Flashing the stock ROM; stock.vzw_root66.tar, kernel, attempting to boot into recovery.
Thank you. Still waiting on this download to Odin the stock image.
If your on a custom rom you will never get a push or OTA from verizon. Also if your stock rooted, you can uninstall all vzw services to block OTA's
When does the custom boot screen come into play? Is this after locking/unlocking the bootloader? Or is this from flashing a custom ROM?
Also the lock icon is in the unlocked position. I'm not sure if this has relation to actually being unlocked or is just a default image showing it's 'custom'
Back up and running! Thank you.
So I've unlocked the boot (will remain unlocked this time) and flashed the following ROM and kernel just as I did last time.
Eschelon's Synergy / Synergy_d2vzw-19Aug12-0509-r39-s
Imoseyon LeanKernel / lk_tw_beta-v0.2.2
Rebooted the device to test and have not received the unauthorized Verizon message yet. The custom boot screen image is gone as well.
thanks for info!
jacksheadache said:
When does the custom boot screen come into play? Is this after locking/unlocking the bootloader? Or is this from flashing a custom ROM?
Also the lock icon is in the unlocked position. I'm not sure if this has relation to actually being unlocked or is just a default image showing it's 'custom'
Click to expand...
Click to collapse
when your bootloader is unlocked the custom unlock screen will go away...reason being there is no longer a secure aboot checking for VZW approved software.
droidstyle said:
when your bootloader is unlocked the custom unlock screen will go away...reason being there is no longer a secure aboot checking for VZW approved software.
Click to expand...
Click to collapse
Thanks again!
Related
I'm having issues getting recovery to work on a Verizon version xoom. I first flashed CWM version 4.0.0.4. The first time I tried to boot into it, it was stuck on the android with the red triangle for a long time before finally getting into it (coincidentally when I was hitting the volume key, don't know if that's related). Anyway, since then I haven't been able to get into it. It will be suck on the red triangle screen for a minute or two before rebooting into the stock rom (I'm running stock ICS). Since then, I've tried flashing the new TWRP 2.2.2 or whatever version it is and it has no effect. It's still doing the same thing. Any clue what's wrong?
So what I'm reading is suggesting that the android guy I'm seeing is the stock recovery. I'm not sure how that's happening. I'm installing the recovery using fastboot on my PC and being in the bootloader on my xoom. The prompts on both appear to confirm success.
I haven't tried this yet as I'm at work, but I think I've got the issue sorted. The following is what appears to be happening from what I've read.
1. I've still got the custom recovery stalled. When the Android guy pops up, one needs to press volume up to enter the options. Otherwise, it reboots.
2. The recovery flashes are taking because I'm booting back into the rom after a flash. The system's built in recovery protection is re-flashing the original recovery at that point.
3. To make my CWM/TWRP/whatever flash stick, I'll need to power down and then boot directly into the recovery.
I'll post again tonight to say if this works. Hopefully this thread can help out others who have the same issue.
If you don't get that to work fastboot img from link..
http://forum.xda-developers.com/showthread.php?t=1074979
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
I unlocked and rooted my tablet yesterday and everything appeared to be working fine. After using it for a couple hours and restarting it a few times it stopped working and is now locked in a boot loop. When I try boot the tablet it comes on and gets to the animation where the glint of light goes across the Asus logo but it does not finish and instead it stops there and I get the moving circles at the bottom. I've left it running there for several hours and it just hangs.
I've tried erasing the data and booting to linux but the same thing happens when I try either of those.
I've also tried flashing a number of different ROMs, but all that happens is it starts installing and then I get the Android guy on his side error screen.
I hadn't done anything to the ROM and was still running 10.6.1.14.4. I even downloaded that same ROM from http://forum.xda-developers.com/showthread.php?t=2266519 but I get the same error message when I try flash that ROM.
I would really, REALLY appreciate any ideas at all - and thanks in advance for any suggestions.
stuck on animation loop
slap_shot_12 said:
I unlocked and rooted my tablet yesterday and everything appeared to be working fine. After using it for a couple hours and restarting it a few times it stopped working and is now locked in a boot loop. When I try boot the tablet it comes on and gets to the animation where the glint of light goes across the Asus logo but it does not finish and instead it stops there and I get the moving circles at the bottom. I've left it running there for several hours and it just hangs.
I've tried erasing the data and booting to linux but the same thing happens when I try either of those.
I've also tried flashing a number of different ROMs, but all that happens is it starts installing and then I get the Android guy on his side error screen.
I hadn't done anything to the ROM and was still running 10.6.1.14.4. I even downloaded that same ROM from http://forum.xda-developers.com/showthread.php?t=2266519 but I get the same error message when I try flash that ROM.
I would really, REALLY appreciate any ideas at all - and thanks in advance for any suggestions.
Click to expand...
Click to collapse
this gonna sound odd but i had exact same prob when i rooted and flashed chromix rom. it went. what i did was flash it once with the rom with secure wipe, then i flashed again. and it got stuck at optimizing apps,then i tried reflashing couldnt get it to boot, what i ended up doing was using clockwork mod to factory reset my tablet, then had to restart, and reflash, this time it actually got to main screen. dont let it discharge/reboot for awhile as im bout to post a issue im having with it. but thats what i did to make it work for me.
shadowarez said:
this gonna sound odd but i had exact same prob when i rooted and flashed chromix rom. it went. what i did was flash it once with the rom with secure wipe, then i flashed again. and it got stuck at optimizing apps,then i tried reflashing couldnt get it to boot, what i ended up doing was using clockwork mod to factory reset my tablet, then had to restart, and reflash, this time it actually got to main screen. dont let it discharge/reboot for awhile as im bout to post a issue im having with it. but thats what i did to make it work for me.
Click to expand...
Click to collapse
I'm not sure I understand --- how do I get to the clockwork mod if i can't get past the startup animation? And I've tried a bunch of roms with secure wipe and i get an error from every one of them.
didnt you install clockwork mod first?
slap_shot_12 said:
I'm not sure I understand --- how do I get to the clockwork mod if i can't get past the startup animation? And I've tried a bunch of roms with secure wipe and i get an error from every one of them.
Click to expand...
Click to collapse
the thing i found showed me to installed the clockwork mod first before i did any flashing, i rooted device then i flashed once clockwork mod was installed, i had to root, then install rom manager and goo manager, from within there i installed the clockwork recovery script/mod then i proceeded to flash chromi-X DEODEX.
Did you flash the correct bootloader? I had the same problem, look for my posts in the last few pages of ChromiX.
Here: http://forum.xda-developers.com/showpost.php?p=41658701&postcount=2716
slap_shot_12 said:
I unlocked and rooted my tablet yesterday and everything appeared to be working fine. After using it for a couple hours and restarting it a few times it stopped working and is now locked in a boot loop. When I try boot the tablet it comes on and gets to the animation where the glint of light goes across the Asus logo but it does not finish and instead it stops there and I get the moving circles at the bottom. I've left it running there for several hours and it just hangs.
I've tried erasing the data and booting to linux but the same thing happens when I try either of those.
I've also tried flashing a number of different ROMs, but all that happens is it starts installing and then I get the Android guy on his side error screen.
I hadn't done anything to the ROM and was still running 10.6.1.14.4. I even downloaded that same ROM from http://forum.xda-developers.com/showthread.php?t=2266519 but I get the same error message when I try flash that ROM.
I would really, REALLY appreciate any ideas at all - and thanks in advance for any suggestions.
Click to expand...
Click to collapse
Seems to me you installed Asus factory stock rom JB 4.2.1 (10.6.1.14.4), which means you have the latest bootloader, then you unlocked and rooted your device, however, you never installed any custom recovery like TWRP or CWM (clockmod). Now your device is boot looping. You need to boot into stock recovery by turn off your device, hold volume down and power button until you see white text on the screen, now release both buttons, you should see 3 icons (RCK, Android and wipe data). NOW you are in fastboot mode. Let me know at least you can get that far, before we continue....
buhohitr said:
Seems to me you installed Asus factory stock rom JB 4.2.1 (10.6.1.14.4), which means you have the latest bootloader, then you unlocked and rooted your device, however, you never installed any custom recovery like TWRP or CWM (clockmod). Now your device is boot looping. You need to boot into stock recovery by turn off your device, hold volume down and power button until you see white text on the screen, now release both buttons, you should see 3 icons (RCK, Android and wipe data). NOW you are in fastboot mode. Let me know at least you can get that far, before we continue....
Click to expand...
Click to collapse
buhohitr -- You're exactly right. I can boot into stock recovery. When I select Android or wipe data it goes back to the animation screen and hangs up. When I select RCK it goes to the Android guy and says installing update but then it show him fallen over and the word Error. I've tried RCK with a memory card that has a number of different ROMs on it but the same thing keeps happening.
slap_shot_12 said:
buhohitr -- You're exactly right. I can boot into stock recovery. When I select Android or wipe data it goes back to the animation screen and hangs up. When I select RCK it goes to the Android guy and says installing update but then it show him fallen over and the word Error. I've tried RCK with a memory card that has a number of different ROMs on it but the same thing keeps happening.
Click to expand...
Click to collapse
Give this a try, the factory Asus firmware zip file that you downloaded, unzip the file, you should see another zip file, rename this new zip file to "EP201_768_SDUPDATE.zip" (without quotation), then copy it to the root of your sdcard then boot into stock recovery and execute the RCK again. Make sure you don't have any other zips laying around in the root of your sdcard.
You are truly a god among men.
buhohitr said:
Give this a try, the factory Asus firmware zip file that you downloaded, unzip the file, you should see another zip file, rename this new zip file to "EP201_768_SDUPDATE.zip" (without quotation), then copy it to the root of your sdcard then boot into stock recovery and execute the RCK again. Make sure you don't have any other zips laying around in the root of your sdcard.
Click to expand...
Click to collapse
THIS WORKED!!! Thanks so much. I was really worried I had bricked it.
So now one last question --- WHY did that work? Is there somewhere I could go to read up on this kind of stuff? I've tried surfing the XDA forum but there's a lot of stuff like this where someone gets there problem solved, but not much explaining why something worked so I can learn more about it.
slap_shot_12 said:
THIS WORKED!!! Thanks so much. I was really worried I had bricked it.
So now one last question --- WHY did that work? Is there somewhere I could go to read up on this kind of stuff? I've tried surfing the XDA forum but there's a lot of stuff like this where someone gets there problem solved, but not much explaining why something worked so I can learn more about it.
Click to expand...
Click to collapse
Somehow the stock recovery was reinstalled on your tablet, thus letting this method work. It however does not on CWM or TWRP. All you did was manually reinstall a stock rom back onto your tablet. How it got the stock recovery is beyond me unless you flashed a stock ROM from CWM and didnt realize what you were installing.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
slap_shot_12 said:
THIS WORKED!!! Thanks so much. I was really worried I had bricked it.
So now one last question --- WHY did that work? Is there somewhere I could go to read up on this kind of stuff? I've tried surfing the XDA forum but there's a lot of stuff like this where someone gets there problem solved, but not much explaining why something worked so I can learn more about it.
Click to expand...
Click to collapse
Since the JB 4.2.1 upgrade, this is the most reliable method to install Asus full stock firmware. Also, since you're unlocked, let root the device by go here http://forum.xda-developers.com/showthread.php?t=2230763 download the tool and root it. Once rooted, I suggest that you should install TWRP custom recovery, by download Goomanager from the market, open the app and tab on the 3 little boxes on the top right hand corner, select "install recovery scripts" , this will shutdown your device and install custom TWRP recovery script, once this installed, you can download "rebooter" from the market and this app has many options, one of them is allowed you easily boot into custom recovery.
Well, after trying to install a ROM through TWRP the phone rebooted and froze on the HTC screen. I then go back into bootloader and try to get into recovery but the splash screen pops up and then the phone reboots. I can get into CWM however when trying to sideload any .zips there I get an error. Not really sure what to do at this point. I probably should have stopped playing with it when I fixed it the first time, ha.
Edit: I fixed my problems! Very happy, ended up restoring some of the firmware from the OTA's and TWRP started working again. Just flashed ROM and fully functionally.
Tim3worx said:
Well, after trying to install a ROM through TWRP the phone rebooted and froze on the HTC screen. I then go back into bootloader and try to get into recovery but the splash screen pops up and then the phone reboots. I can get into CWM however when trying to sideload any .zips there I get an error. Not really sure what to do at this point. I probably should have stopped playing with it when I fixed it the first time, ha.
Edit: I fixed my problems! Very happy, ended up restoring some of the firmware from the OTA's and TWRP started working again. Just flashed ROM and fully functionally.
Click to expand...
Click to collapse
which ota did you flash? what network provider you on? im having same problems, did you flash ota in twrp?
tr1gg3r84 said:
which ota did you flash? what network provider you on? im having same problems, did you flash ota in twrp?
Click to expand...
Click to collapse
My provider is AT&T. I used the UK OTA from this link http://db.tt/LrIEemZ4 . Its part of this thread in general http://forum.xda-developers.com/showthread.php?t=2422885. Basically what was happening is that I had flashed a ROM which didn't work out and so it would just hang on the white HTC screen. I figured no big deal I'll just go into recovery and flash another one I know works. That didn't work out. Any time I tried to go into recovery the TWRP splash screen would pop up for a second then the phone would reboot. Which kind of had me puzzled because I flashed ClockWorkMod for recovery and it would at least get me into recovery but still adb sideload was giving me errors so I flashed TWRP again even though it wasn't working either.. I pulled the boot.img out of the Firmware.zip in the OTA and flashed that with fastboot. At that point I had tried just about everything and was about to give up but to my surprise that seemed to fix it. I was able to go into recovery no problem. Sideloaded the ROM and everything went great. I'll probably not be messing with my phone like that for a bit haha. It was the second night in a row that I had wiped an OS off the phone and struggled to figure out how to get it working. Glad its all good now though. Good luck to you!
cant change recovery / device rebooting
Hi, i have a similar problem,
I've unlocked with htcdev everything is fine.
Then I installed Twrp-2.6.0.0.img as recovary.
I'm not able to mount the internal storage, so I had to push the ROMs via ADB.
starting a ROM 1st time seems to be ok.
restart is also ok.
shutdown and power on is rebooting every ~15sec.
I tried to change my bootloader.
fastboot flash recovery recovery-clockwork-touch-6.0.3.6-m7ul.img -> volume keys are responding
fastboot boot recovery-clockwork-touch-6.0.3.6-m7ul.img -> volume keys are NOT responding
recovery isn't starting until i run following commands:
fastboot flash recovery Twrp-2.6.0.0.img -> volume keys are responding
fastboot boot Twrp-2.6.0.0.img -> volume keys are NOT responding
but after resetting the device + entering recovery it's there
thanks for your ideas/help
I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
The following thread had a similar problem and was fixed... http://forum.xda-developers.com/showthread.php?p=53404637
NerdNoob1210 suggested...
"If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose."
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
If not how can I force it into bootloader instead please ? any suggestions appreciated.
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?