Database Develop

Huawei Ascend P7 Bootloop

Hello,
Yesterday I was trying to root my phone and install a newer Rom. Rooting my phone was no problem (I used the KingUser Desktop app), but after that my phone restarted and kept loading the Huawei Logo...
I desperately tried to use this guide: http://forum.xda-developers.com/ascend-p7/help/huawei-p7-bootloop-t2904049 And followed the steps of the user "Wekii", but it didn't work at all...
I got to step 13, but then when "android system recovery 3e" tries to verify the file it gets stuck.
I used this Rom: http://www.carbontesla.com/2014/09/...t-firmware-ascend-p7-l10-v100r001c00b133sp01/
Can somebody point me in the right direction?
Kind regards,

Hi,
Firmware/emui version before root?
Firmware/emui Version you have flashed after root?

I have the same problem. I was on this ROM:
http://forum.xda-developers.com/ascend-p7/development/rom-myrom-v1-0-emui-2-3-4-4-2-b135-t2948887
I wanted to go to stock, so I downloaded an official UPDATE.app and flashed stock recovery.img and boot.img.
I downloaded Sophia-L10_V100R001C00B621_Firmware_West European Region_Others_Android 4.4.2_EMUI 3.0_05012HCE.zip from http://consumer.huawei.com/nl/support/downloads/
I flashed stock 621 boot.img and recovery.img.
Now it is in a bootloop. I can't enter recovery or fastboot. All I see is the Huawei logo boot loop, no matter what I do.

You have to go back via transition pack. Then it works fine

I formatted the SD card, copied the transitional UPDATE.APP from the official site, yet it's still doing the same. Just the logo, nothing else. I started it while holding all three buttons.
After trying to force load the transitional package, now the phone boots up with the logo, but at least it isn't rebooting. It does turn off by itself after some time. I tried to update the second package and the logo just stays on indefinitely.

You have to follow the rollback instructions. Dont easy flash the pack.
This instructions are right. Think that in your versions.
View attachment 3492003

I'm sorry, but I cannot follow the instructions as they tell me to do this through the phone menu. Unfortunately I no longer have a phone menu since I cannot boot up my phone. I thought the alternative would be to try force update with both volume buttons and power.
---------- Post added at 10:12 PM ---------- Previous post was at 09:45 PM ----------
Okay, I managed to get into fastboot & rescue mode. White screen. I will see what I can do from here.
---------- Post added at 10:57 PM ---------- Previous post was at 10:12 PM ----------
I couldn't get any update.app to be installed. I flashed My-RoM v1.2 / EMUI 2.3 again. (http://forum.xda-developers.com/ascend-p7/development/rom-myrom-v1-0-emui-2-3-4-4-2-b135-t2948887)
It is functional, but I don't know how to go back. I am on EMUI 2.3, but I think I need a stock recovery/boot.img and UPDATE.APP. But which one will work?
I don't care which version I will be on. I just want to be on stock.

Nexus 6 turns itself off after flashing 6.0 factory image with modified system image

Hi guys,
After flashing my nexus 6 with the 6.0.0 factory image which came out this morning and modified the system image when first enter TWRP recovery, my device is unable to boot. It will just shutdown after the "Your device is corrupted ..." message. Anyone else has issue like this?

i have the same issue
---------- Post added at 03:49 PM ---------- Previous post was at 03:40 PM ----------
well I just pressed all the buttons and tapped all over the screen lol and it booted up. don't know what exactly what did it
now every time I reboot the phone i get the same "Your device is corrupted ..." message, but it boot up on its own

jblack41510 said:
i have the same issue
---------- Post added at 03:49 PM ---------- Previous post was at 03:40 PM ----------
well I just pressed all the buttons and tapped all over the screen lol and it booted up. don't know what exactly what did it
now every time I reboot the phone i get the same "Your device is corrupted ..." message, but it boot up on its own
Click to expand...
Click to collapse
After lots of try and error, now my N6 boots up without the annoying message.
1. Flash 6.0.0 factory image via fastboot.
2. Boot into system and so some initial setups. (I still see the message even after flashing the f actory image, sigh).
3. Flash custom kernel (I am using leankernel for M preview 3) and reboot.
4. Flash latest TWRP. (Select not to install supersu upon exiting) and reboot.
5. Flash Supersu2.4.6 zip and reboot.
6. Bingo, The message disappeared!
It's really weird.

redlee90 said:
After lots of try and error, now my N6 boots up without the annoying message.
1. Flash 6.0.0 factory image via fastboot.
2. Boot into system and so some initial setups. (I still see the message even after flashing the f actory image, sigh).
3. Flash custom kernel (I am using leankernel for M preview 3) and reboot.
4. Flash latest TWRP. (Select not to install supersu upon exiting) and reboot.
5. Flash Supersu2.4.6 zip and reboot.
6. Bingo, The message disappeared!
It's really weird.
Click to expand...
Click to collapse
After flashing the custom kernel you're rebooting into bootloader? Or into System? If system does the message pop up with the custom kernel?
Perhaps it's the kernel that causes the error but I don't understand why it pops up even after flashing the factory images. :/

Got a used N6 and it won't boot.. No system?

Looking for an answer I have not been able to find as to recovering a used N6.
What I have is a used N6, with TWRP 6.8.7.1 (newest version I believe) no recovery files and does not appear to have a working system on it. The bootloader has been relocked (won't allow unlocking or reflashing of stock firmware). What I am guessing is some one unlocked it, modified it, and relocked it then somehow messed up and wiped the system ... Guessing.
It has the older 71.10 bootloader on it now, not sure if it updated beyond 5.11 or not.
Just thinking (as I write this) would it be possible to make an image of another N6 put it on a OTG thumb drive and restore that or if possible push recovery files through Fastboot or possibly ADB in recovery?
Or am I out luck?
Any know fixes?

My recommendation would be to push files through fastboot. Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
As a note, I recently had to go through this process and the FLASH ALL file was failing to flash the system file. The answer was to manually flash each file myself (directions provided in the same post). It was fairly easy once I realized the issues with FLASH ALL.

As soon as you get android booting, go back and unlocked the bootloader. I don't get all these people locking their bootloaders... ESPECIALLY with a rom and custom recovery!
The above is almost the right advice, but IIRC it wont work with a locked bootloader.
Fortunately you have TWRP installed. Don't mess with your recovery partition until you get this sorted.
Just go download a rom, any will probably work... I would stick with an AOSP one and maybe download the 5.1.1
You may be able to just mount the phone as an MTP device, I think that may be supported by TWRP at this time? Or sideload/push.
Gimme a sec, I'll post some links
---------- Post added at 01:29 PM ---------- Previous post was at 01:14 PM ----------
As I said most roms will probably be OK, But to be specific I would just grab a 5.1.1 version of pure nexus... say the last 5.1.1 version
https://www.androidfilehost.com/?w=files&flid=34545
Download page for pure nexus (this does not include gapps)
Specifically I would download this one, as I said its the last 5.1.1 version. I say this because the bootloader should be fine with it whether its updated or not (I couldn't find a list of what bootloader is what version)
https://www.androidfilehost.com/?fid=24052804347817485
Boot to recovery, and see if your phone shows up under my computer. MTP transfer should be enabled by default in TWRP and is supported by TWRP version > 2.8
If you can't get it to show up as an MTP device, you should be able to see it with ADB while booted into TWRP. Use either the push command
http://stackoverflow.com/questions/...mand-to-push-a-file-on-device-without-sd-card (discussion on push)
push maybe to /sdcard if the directory exists.
I'd probably just use sideload though,
https://twrp.me/faq/ADBSideload.html
One of these should work
---------- Post added at 01:37 PM ---------- Previous post was at 01:29 PM ----------
I'll leave it to you to find gapps for 5.1.1
I don't think you would need them though as android should still load and work fine with out them. I would simply start up the phone with the rom installed, turn on allow oem unlock, boot immediately back into bootloader and unlock the boot loader. If something happens to that recovery partition the phone is a paperweight with the bootloader locked... really not worth keeping it locked.
Once you get the bootloader unlocked, update to something current and worry about gapps then?

Thank you so much guys!! Will give this run as soon as I have a chance and update the post(may take a day or so been pretty busy at work and such)
UPDATE : @scryan Hey just want to say that did the trick, had to use a thumb drive and OTG cable to load the ROM. But was in and out with an now unlocked bootloader in under 30 minutes.
Thanks again guys!!

[SOLVED] Stuck in "warning bootloader unlocked" screen. Device won't turn OFF.

[SOLVED] Stuck in "warning bootloader unlocked" screen. Device won't turn OFF.
Hi all,
I have a Moto G 2014 (Titan, XT1068).
I am not new to custom ROM-ing and Android hacking, had all 4 of my personal Android phones unlocked and rooted just fine - I usually know what I'm doing.
This here is my mom's phone and it's the first Moto G 2014 I attempted to unlock & root so far. I know the basics, but this particular device gives me headache...
All actions were performed on 07. October 2016 after carefully researching the latest HOW-TOs for the Moto G 2014 on XDA and other websites:
- I unlocked the bootloader using the official process from Motorola to receive the "unique key".
- I installed twrp-3.0.2-3-titan.img recovery.
- I downloaded SR1-SuperSU-v2.78-SR1-20160915123031.zip and placed it on storage.
- I booted into TWRP recovery, installed SuperSU and Wiped Dalvik+Cache, then rebooted.
Since then, I am stuck in the "warning bootloader unlocked" (WBU) screen and the device won't turn off.
If I press the power button and hold it for a few seconds, normally it turned the device off, but now it just reboots into the WBU screen, looping forever.
- I can still enter my fastboot by holding VOL-down + Power, get a adb connection with my Android SDK + platform tools on my Windows and issue adb and fastboot commands normally.
- I can still enter the recovery and do stuff with it normally.
Since this incident, I have also tried a normal Wipe (whatever the default wipe settings are) in TWRP, no change / effect.
I have no clue what to do next, other than wait for the battery to go empty that is, since I can't even turn the device off.
Some methodologically sound advice would be highly appreciated at this point. :good:
Thank you in advance.

You just can't flash the supersu file in twrp before flashing the supersu you need to flash roo.M.br.zip file in fastboot mode then you can flash the SuperSU.
The file available at stock firmware section.
---------- Post added at 09:48 AM ---------- Previous post was at 09:46 AM ----------
Flash the stock rom from fastboot mode then again root the device as i said it will solve the problem.

Prasourabha said:
You just can't flash the supersu file in twrp before flashing the supersu you need to flash roo.M.br.zip file in fastboot mode then you can flash the SuperSU.
The file available at stock firmware section.
---------- Post added at 09:48 AM ---------- Previous post was at 09:46 AM ----------
Flash the stock rom from fastboot mode then again root the device as i said it will solve the problem.
Click to expand...
Click to collapse
Is this roo.M.br.zip file included in the Stock Rom or is it the Stock Rom itself?
Or is there another general name for this roo.M.br.zip? Because I can't find it via the search function of the forum.
Anyhow ... in the meantime I will be downloading XT1068_TITAN_RETAILDSDS_5.0.2_LXB22.99-16.3_Easy_Installer.zip which is linked on the following thread:
- http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
- first URL for XT1068 labeled as "***NEW*** DOWNLOAD XT1068 5.0.2 LXB22.99-16.3 RETDSDS WITH STAGE FRIGHT FIX RETAIL DUAL SIM DUAL STANDBY (EU/INDIAN/GLOBAL) 26/08/2015 BUILD ***NEW***"
But I already had a look into the archive, nowhere to find a roo.M.br.zip is even similarly named file(s).
Could you be a little more specific or provide the correct XDA thread / link?
Also, the fact that "I can't just flash SU" it must be device specific, right?
Because on my other Android phones I just installed/flashed SU via recovery mod with no problems and that was it.
EDIT: also, according to this guide here, apparently you "can just install SU", if I understand correctly and it's more or less exactly how I proceeded (unless wiping cache/dalvik after flash was harmful):
- http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2nd-gen-2014-t2874245

Here is the link of the page where yiu can find the file and the rooting guide
http://forum.xda-developers.com/moto-g-2014/general/root-root-moto-g-2014-android-t3255711

Prasourabha said:
Here is the link of the page where yiu can find the file and the rooting guide
http://forum.xda-developers.com/moto-g-2014/general/root-root-moto-g-2014-android-t3255711
Click to expand...
Click to collapse
Sorry for not understanding your answer at first.
Obviously you were refering to two different things in one post and I was a little confused.
- RESTORING THE STOCK-ROM BASED ON MARSHMALLOW / ANDROID 6.0 HAS BROKEN THE BOOTLOOP IN THE UNLOCKED BOOTLOADER WARNING.
The other issue was obviously that you catched what I wanted to do originally, which was to ROOT the device.
- DOWNLOADING AND FLASHING THIS "root-titan-M-BR.zip" IN THE THREAD YOU SPECIFIED ENABLED ME TO FLASH SUPERSU AFTERWARDS WITHOUT PROBLEMS.
Obviously I can now go on doing what I initially intended, which is installing CM13 on my mom's phone.
I almost thought I had bricked the phone for good.
Thank you for your support. :good:

MotoG5S plus on bootloop Need to verify this fix that im trying.

Out of nowhere, my phone entered a reboot loop.
The only 'modding' i ever did was use platform tools to allow tasker access to my wifi, that was over a week ago, so im baffled im having to deal with this as i have never tried to root the phone or flash a new OS or anything, , i even avoided Updates as they tend to be buggy.
Either ways, i searched the forum and found out id have to flash a stock ROM to fix the device, now there are a few things that arent clear to me.
A) I am able to access the recovery mode and select factory reset. is flashing a ROM any different than this?
B) Does this mean im 'rooting' my device?
C) Can i save my DCIM/ Downloads data by flashing (have no kind of recovery set up).
some post said if the same version or ROM is flashed then the 'userdata wipe' command may be skipped
Im note sure what OS or Security patch version im running.
in the boot menu the Baseband is showing as <unavailable>
in the recovery menu i see something like sanders_retail_8.1.0_opss28.65-36-3/4af3
I have downloaded a ROM named SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml , but havent tried to flash it yet.
My region is INDIA (same as brazil retail i think) , and im really hoping to fix this issue without having to wipe my data, any help would be much appreciated, thanks.

1>Flashing rom is completely different than factory reset from recovery mode. You have to flash stock firmware from fastboot mode.
2>Your phone won't get rooted if you flash stock rom instead if your phone is rooted it will unroot it.
3>There is no way of flashing stock rom without formatting data as in order to flash any rom you need an unlocked bootloader and unlocking bootloader deletes all files

paradox99 said:
Out of nowhere, my phone entered a reboot loop.
The only 'modding' i ever did was use platform tools to allow tasker access to my wifi, that was over a week ago, so im baffled im having to deal with this as i have never tried to root the phone or flash a new OS or anything, , i even avoided Updates as they tend to be buggy.
Either ways, i searched the forum and found out id have to flash a stock ROM to fix the device, now there are a few things that arent clear to me.
A) I am able to access the recovery mode and select factory reset. is flashing a ROM any different than this?
B) Does this mean im 'rooting' my device?
C) Can i save my DCIM/ Downloads data by flashing (have no kind of recovery set up).
some post said if the same version or ROM is flashed then the 'userdata wipe' command may be skipped
Im note sure what OS or Security patch version im running.
in the boot menu the Baseband is showing as <unavailable>
in the recovery menu i see something like sanders_retail_8.1.0_opss28.65-36-3/4af3
I have downloaded a ROM named SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml , but havent tried to flash it yet.
My region is INDIA (same as brazil retail i think) , and im really hoping to fix this issue without having to wipe my data, any help would be much appreciated, thanks.
Click to expand...
Click to collapse
Factory reset, wipes user data, it doesn't restore firmware.
To flash correct firmware, you should know
Model#, codename, software channel and software version
Run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
See
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
If you don't know fastboot commands
Motorola Flashing Guide
You can skip
erase userdata but doesn't mean device will boot.
If bootloader is locked, likely will not be able to flash with fastboot.exe
Sent from my ali using XDA Labs
---------- Post added at 07:50 PM ---------- Previous post was at 07:45 PM ----------
A option for locked bootloaders
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
There is a possible way to skip data wipe, described in that thread.
Sent from my ali using XDA Labs