Develop Bugs

Having trouble with recovery and download mode

I got a hand me down S3 since my old phone (ancient infuse 4g) recently broke. It works fine at the moment, but I can't seem to get anything to work properly in terms of roms/odin/any customization.
Booting into download seems to work, as I can flash things in ODIN, but it shows a black screen. I've been using adb boot download to make sure I'm going into the right mode. ODIN shows success when flashing stuff, but I'm not so sure.
Booting into recovery just shows a black screen. Flashing to stock recovery, cwm, or twrp doesn't seem to change anything.
I can't get any of the root methods to work since I can't get into recovery. I found a rooted stock image that's current but it's in zip form, and since you can only install zip files from recovery, I can't use it. I tried a convert to tar utility but that also didn't work.
I've done a factory reset, and managed to wipe everything the one time I got into stock recovery (when I first got the phone). After that, any attempts to root, get back to stock, or do anything really but turn it on and use it, aren't working. I also tried towelroot, which worked once, then I reset the phone and towelroot no longer worked- probably due to a kernel upgrade.
A lot of the posts I found, including one about Kies, all dealt with older versions and possible bricking when downgrading bootloaders so I wanted to make sure before I did anything dumb.
Oh, and using rom manager to try to install cwm just freezes at 'flashing'. the twrp utility whose name I forget (replaced goo manager) just freezes as soon as I open it. I've also tried multiple usb ports, and made sure to only use ones directly connected to the mother board.
I'm running ucufnj1. Maybe if I had an odin flashable version of that?
What do?

Did you try flashing a custom recovery in Odin? When it finishes flashing recovery, do not let it reboot. Just remove the battery and try booting into recovery.
I recommend using Philz Touch for the d2lte.

audit13 said:
Did you try flashing a custom recovery in Odin? When it finishes flashing recovery, do not let it reboot. Just remove the battery and try booting into recovery.
I recommend using Philz Touch for the d2lte.
Click to expand...
Click to collapse
I tried that with cwm and twrp, removing the battery and all, but I got a black screen with both. Just an unresponsive black screen.

Please help!

yoonietang said:
I tried that with cwm and twrp, removing the battery and all, but I got a black screen with both. Just an unresponsive black screen.
Click to expand...
Click to collapse
Are you checking auto-reboot in Odin?

audit13 said:
Are you checking auto-reboot in Odin?
Click to expand...
Click to collapse
I make sure auto reboot is unchecked, then I take the battery out and try to start into recovery. I'm also having trouble booting into download mode with the button combo (vol down, home, power) so I've been using adb reboot download to do it.

Can you use adb commands to enter recovery?
Have you tried flashing the latest Philz Touch doe thr d2lte? I highly recommend it.

audit13 said:
Can you use adb commands to enter recovery?
Have you tried flashing the latest Philz Touch doe thr d2lte? I highly recommend it.
Click to expand...
Click to collapse
Doesn't work =( Still getting the same black screen when I try to get into recovery.

If you can somehow manage to get into download mode, let me know what it says on the screen. The important thing is to make note of the model # and the presence of a warranty bit line.
If you can't get into download mode, try installing the Samsung Info App from the Play Store and use the app to find your bootloader and modem version.

audit13 said:
If you can somehow manage to get into download mode, let me know what it says on the screen. The important thing is to make note of the model # and the presence of a warranty bit line.
If you can't get into download mode, try installing the Samsung Info App from the Play Store and use the app to find your bootloader and modem version.
Click to expand...
Click to collapse
I honestly can't tell if I'm getting into download mode or not. I *think* I'm getting into download mode except with a black screen for some reason, as ODIN claims success when flashing stuff. I also used adb reboot download to eliminate any doubt about holding the right buttons to access it, so that helps narrow down the possible source of the problem. I believe my dad (previous owner) had the screen replaced at some point. Could this be a wobbly connection?
Phone model is sgh-i747rwbatt.
Bootloader, Baseband, PDA, and CSC versions are all UCUFNJ1 (csc is i747attfnj1).
I can't seem to find modem version- is that baseband? Modem model is MSM8960.

Weird but the AT&T S3 is the sgh-i747. There should not be any letters or numbers after the second 7.
In download mode, are you seeing the Android guy? Are you sing the button combination or fastboot commands to get into download mode? USB debugging must be on to use fastboot commands.

audit13 said:
Weird but the AT&T S3 is the sgh-i747. There should not be any letters or numbers after the second 7.
In download mode, are you seeing the Android guy? Are you sing the button combination or fastboot commands to get into download mode? USB debugging must be on to use fastboot commands.
Click to expand...
Click to collapse
just had to go there. 1st three google search results for sgh i747rwbatt pulled up a white S3. (?). never knew or heard of.
"all i can really do , is stay out of my own way and let the will of heaven be done"

audit13 said:
Weird but the AT&T S3 is the sgh-i747. There should not be any letters or numbers after the second 7.
In download mode, are you seeing the Android guy? Are you sing the button combination or fastboot commands to get into download mode? USB debugging must be on to use fastboot commands.
Click to expand...
Click to collapse
usb debugging is on. Download mode just shows a black screen, nothing at all, whether I use adb reboot download or the button combo to get into. Odin reports that it sees the phone though.

would like to get @audit13 opinion on this , but you can use flashify and mobile odin to flash with. i have no experience with mobile odin and have only used flashify for .img and not .zips. he might be more knowledgeable about these apps performance records.
"all i can really do , is stay out of my own way and let the will of heaven be done"

Since the LCD remains black when you boot into download mode, I assume you obtained the phone information using the Samsung Phone Info App.
Are you able to issue fastboot commands in download mode? In download mode, does fastboot devices return your phone?
Unfortunately, I know nothing about mobile Odin or Flashify. I have never used these tools and don't have an s3 anymore.

audit13 said:
Since the LCD remains black when you boot into download mode, I assume you obtained the phone information using the Samsung Phone Info App.
Are you able to issue fastboot commands in download mode? In download mode, does fastboot devices return your phone?
Unfortunately, I know nothing about mobile Odin or Flashify. I have never used these tools and don't have an s3 anymore.
Click to expand...
Click to collapse
Fastboot commands don't work. I tried installing the fastboot drivers, but I still get nothing returned when I try 'fastboot devices', so I couldn't try any of the other fastboot commands. I'm not 100% sure if it's the drivers on my PC or the phone that's the issue, since a lot of the samsung/google drivers seem a bit finicky, but I did install minimal adb and fastboot from this forum.
Yes, I used the samsung phone info app (it's not official, right? It's made by vndnguyen?).
In regards to odin mobile and flashify, when I googled flashify (someone else mentioned it on reddit when I asked there) it said it required root. Unfortunately, I still can't get root due to the recovery issues, or I'd be able to use any number of methods.

When you try to enter download mode, do you see the warning screen where you press the volume key to continue to download mode?
Since you can't issue fastboot commands, this leads me to believe that the phone may not be entering fastboot mode. In fastboot mode, you may be able to push a recovery image to the phone.
Could you post a screen shot of your Odin screen with the phone connected?

audit13 said:
When you try to enter download mode, do you see the warning screen where you press the volume key to continue to download mode?
Since you can't issue fastboot commands, this leads me to believe that the phone may not be entering fastboot mode. In fastboot mode, you may be able to push a recovery image to the phone.
Could you post a screen shot of your Odin screen with the phone connected?
Click to expand...
Click to collapse
When I boot into download or recovery, there is nothing but a black screen, nothing else at any point at all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Again, nothing but a black screen when I boot to recovery or download. I do get the vibration to confirm the device turning on though.
Also a screenshot showing fastboot

When using the button combination for download mode, I believe the first screen you see is a warning screen, then you need to press the volume + key to enter download mode. Are you pressing the volume up key?
Open Odin, flash recovery, and then take a screen shot of the Odin screen after it finishes flashing recovery. This may provide more clues as to what's happening.

audit13 said:
When using the button combination for download mode, I believe the first screen you see is a warning screen, then you need to press the volume + key to enter download mode. Are you pressing the volume up key?
Open Odin, flash recovery, and then take a screen shot of the Odin screen after it finishes flashing recovery. This may provide more clues as to what's happening.
Click to expand...
Click to collapse
Same when I try twrp of philz touch. However, when I flashed philz and then booted into recovery, I get a vibration when I touch the screen. This leads me to believe that the recovery is active, but the screen is off for some reason. Maybe if someone could walk me through flashing an image from recovery, step by step, I could do it blind?
Also, it seems that booting into download via key press requires you to press the volume up button to active download mode but using adb reboot download does not (based on when odin/my PC detected the phone entering download mode). Regardless, I tried both ways.
Edit: I copied and pasted the OP from another forum, and didn't realize it cut something off- I believe that my dad at some point had the screen replaced. Could it be a loose connection? It seems unlikely since I managed to get into recovery once when I first received the phone.

[Q] How To Get Custom Recovery??? [HELP]

The one or two threads I read already expect you to be on a custom rom and have some recovery, when in fact I believe if coming straight from Stock Recovery and Stock Rom, then Stock Recovery WON'T Let you flash a custom recovery...
So how then? Could I just root my LG Optimus G Pro (E980) with maybe TowelRoot and then install from Play Store Flashify and load a custom recovery img off this thread http://forum.xda-developers.com/opt...overy-zip-twrp-2-8-1-0-lg-g-pro-e980-t2967855 and attain getting a custom recovery?

How do I get into Custom recovery, not sure if it took, it said insecure boot and something else after rebooting from flashify do I hold power and volume up or down and home key or?
"Secure booting error
Cause: boot certification verify"
Is what it exactly says...

Finally after playing around some I installed GPRO_Recovery_6.0.4.4.apk and then got CWM to install somehow I noticed moved twrp zip to the innersd card since for some reason cwm didn't wanna go into extsd card and then flashed twrp 2.8.1.0 successfully.

I should retitle this half baked TWRP Semi functionality with ZER0 Community Support. LoL
Is there a flashable zip of CWM and no one still told me how to enter security, I'm now getting a double LG Splash screen and second one just sits and hangs, trying to install either PhilZ recovery with hopes of it detecting my external sd card unlike the half baked TWRP with semi functioning touchscreen drivers.
So again, I know I do or think it's powered off Volume Up and Power button, but how long do I hold in the power button, 3 seconds, 5 seconds, 10 seconds, 15 seconds? Too long and not releasing it just shuts the phone down.
Am I gunna get any help or is this all echoed shots in the dark thrown out aimlessly that nobody GAD to answer and help out?
It's important to me to have a fully functioning recovery, I don't wanna boot into the darn thing just to look at the screen and not do diddly squat with.

To get to the recovery screen with power + volume up button at the same time. There is a version of cwm 6.0.47 that's in flash able zip file, you can get it in the optimus general section. That's the most reliable version, it will not cause you the recovery boot loop. The easiest way is to use freegee if you haven't try it already.

How many fracking times to I gotta boot into TWRP before damned touchscreen decides to work again, jesus christ I wanna murder the dumba55 who released this half baked nonsensical p.o.s. it's bloody b.s. I swear to god!!!

There is a better version of Twrp in the lg optimus g pro original Android development section. It still doesn't read the external SD card thought.

hawkwind212 said:
There is a better version of Twrp in the lg optimus g pro original Android development section. It still doesn't read the external SD card thought.
Click to expand...
Click to collapse
Thanks finally I got a rom to install by copying it to internal storage while booted up in TWRP, used MiUi now to install FreeGee and try to get CWM to install again.

There is a zip file of cwm you can flash from Twrp in the optimus general section if freegee doesn't work out. It's the same version as the freegee 's. However, it's not a touch screen version of cwm, but it will not get you into the recovery boot loop when you open the recovery with power+volume up buttons.

hawkwind212 said:
There is a zip file of cwm you can flash from Twrp in the optimus general section if freegee doesn't work out. It's the same version as the freegee 's. However, it's not a touch screen version of cwm, but it will not get you into the recovery boot loop when you open the recovery with power+volume up buttons.
Click to expand...
Click to collapse
How do we fix the bootloop in PhilZ recovery?
---------- Post added at 12:41 PM ---------- Previous post was at 11:49 AM ----------
Looks like I'm gunna be flashing stock all over, last night I changed my build.prop in CloudyGX_V1.0 cause I thought it needed it, then it wouldn't boot up at all this morning, so I went into PhilZ recovery and reflashed CloudyGX_V1.0 and it successfully installed but wouldn't get out of reocovery bootloop, so I tried flashing this (worksinallrecovery)TWRP-2.6.1.0-E980-LOKIFIED.zip and now it acts as if there's no recovery at all installed and just sits at the one LG splash screen, no double lined white font message or anything, just sits and sits and sits there doing nothing.

Trying this: http://forum.xda-developers.com/showthread.php?t=2302660 and I can't even get it to go into download mode... Guess it's time to take the phone to a repair shop and see what they can do, I don't get it though I just flashed another recovery zip found here file found here: https://docs.google.com/file/d/0BziXHIJy7TsjZ0xqd0RNQWNGV0k/edit in PhilZ and then this started happening, I extracted the recovery zip zipped in together with everything else and then bam.

I did later on realize that half a minute or so after TWRP loads then finally touchscreen starts working, I just wished external sd card would be picked up in it.

Yea, I was going to tell you to flash Twrp to get out of the boot loop or there is a zip file just for getting out of the recovery boot loop. Look on philosophy thread for more info on that. Also, there is suppose be a script that fix the recovery boot loop with the touch version of cwm, but I not sure how well it works, that's why I stay with version 6.0.47. Too bad that Twrp doesn't read the SD card, it looks good though other than that.

hawkwind212 said:
Yea, I was going to tell you to flash Twrp to get out of the boot loop or there is a zip file just for getting out of the recovery boot loop. Look on philosophy thread for more info on that. Also, there is suppose be a script that fix the recovery boot loop with the touch version of cwm, but I not sure how well it works, that's why I stay with version 6.0.47. Too bad that Twrp doesn't read the SD card, it looks good though other than that.
Click to expand...
Click to collapse
Waiting to hear back from the cellphone repair store, I was completely stuck, it wouldn't do anything. So I guess after that hopefully start back at square 1.

Well the cellphone repair store said they ran all the software they could find for the LG Optimus G Pro (E980) and still couldn't get it to come out of the very first LG Splash screen, looks like maybe now it's time to send it in to be JTAG'ed and hope that fixes it.

I'm having a similar issue, after I rooted with Optimus G Pro Manual Root Tool, I used GProRecoveryTool to install cwm. But after I got into CWM I tried the installing this twrp zip and ever since I tried booting I'm greeted with "Secure Booting Error! Cause : boot certification verify". I can't boot into recover nor rom lol. Easy on me though, it's my first LG device
I also just noticed that It's not recommended to install on stock rom....well I did haha

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What next? Someone told me to hold down both volume keys and plug in the phone to my computer and viola I got into download mode...
I'm asking here cause some of the LGFlashTools Tutes are for different models, using I guess LGE980_20130314_LGFLASHv151
Do I just click OK button no need to do anything PRL & SCRIPT and keep UPGRADE DL Checked and USB?
I've got the BIN_LGE980AT-00-V20g-ATT-US-APR-28-2014+0.tot file

Emmanuel U said:
I'm having a similar issue, after I rooted with Optimus G Pro Manual Root Tool, I used GProRecoveryTool to install cwm. But after I got into CWM I tried the installing this twrp zip and ever since I tried booting I'm greeted with "Secure Booting Error! Cause : boot certification verify". I can't boot into recover nor rom lol. Easy on me though, it's my first LG device
I also just noticed that It's not recommended to install on stock rom....well I did haha
Click to expand...
Click to collapse
Usually after that screen custom recovery should load. I'm awaiting further steps to my above posted question.

n1nj4Lo said:
Usually after that screen custom recovery should load. I'm awaiting further steps to my above posted question.
Click to expand...
Click to collapse
I can't boot into recovery or rom, only download lol. I'm gonna be trying this soon.

n1nj4Lo said:
What next? Someone told me to hold down both volume keys and plug in the phone to my computer and viola I got into download mode...
I'm asking here cause some of the LGFlashTools Tutes are for different models, using I guess LGE980_20130314_LGFLASHv151
Do I just click OK button no need to do anything PRL & SCRIPT and keep UPGRADE DL Checked and USB?
I've got the BIN_LGE980AT-00-V20g-ATT-US-APR-28-2014+0.tot file
Click to expand...
Click to collapse
Is that the version you got of the xda ogp forum here? Yes, it's usually with the usb cord plug into your device already, hold down both volume and power buttons at the same time, then plug the other end of cord into your computer. If that doesn't work, some time take out the battery helps. I forget the steps, but follow the soft brick repair guide and you will not go wrong. Also, if you do get it to start flashing, make sure you get a 100% completion, do not interruption the flash process regardless what the guide says.

[Tutorial] Flash/Root/update elephone P8000

I know what you are thinking: "Another root/flash tutorial??, it's already explained multiple times right?"
Yes that's true. But for some reason it did not work when I followed the exact steps described (I tried it on 2 different elephone P8000 phones), and I believe I'm not the only one so i created this post to help others.
I folled these step: bbs.elephone.hk/thread-6616-1-1.html#.VkcZqL8WCnN (the guide link in the "Eragon v.5.9.2" thread.
Flashing instructions:
1. Install the usb drivers and reboot your PC.
(Download link: mega.co.nz/#!55BQkKiR!OPBrnj7SXxsUbuchAjV8orT9SMAOMpbDesYTMO2DDHY)
2. Check if the drivers are installed correctly.
Go to "Device manager" on your windows PC and check if there are no yellow question marks appearing when connecting the phone to the PC​3. Download the flashtool and firmware you would like to flash:
Latest version of the Flash tool: (androidmtk.com/smart-phone-flash-tool)
Stock Rom from official forum: (bbs.elephone.hk/forum-270-1.html#.Vkcc878WCnM)
Eragon ROM: (forum.xda-developers.com/elephone-p8000/development/rom-06-9-eragon-1-0-android-5-1-t3195007)
Philz recovery Touch 6.59.0 Port P8000 Version 2: (forum.xda-developers.com/elephone-p8000/development/recovery-philz-touch-6-59-0-port-p8000-t3224478)
?CWM Recovery (didn't work for me): (bbs.elephone.hk/thread-6616-1-1.html#.VkceZL8WCnN)
4. Open the flash tool and select the scatter download file included in your firmware you downloaded.
!the next steps differ from every tutorial I've read but seem to work perfectly.
5. Turn your phone on (normal no recovery).
6. Click on the download button in the flash tool.
7. turn your phone off (the normal way)
8. The flashing should automatically start while the phone is turning off.
9. Wait for the conformation in the flash tool (green check mark).
10. Remove the usb cable from the phone and hold to power button till the phone boots.
To root:
Just install superSU from the playstore and root. (confirm with rootchecker app, also from the playstore).
If that does not work for you. Install a custom recovery following the flash instructions above. Put de SuperSU binary's on your sd card. Boot into recovery by turning off your phone. Now hold the power and volume up buttons till you see a selection menu. Select "recovery" with the volume up button and confirm using the volume down button. In recovery use the install from zip function to install the superSU binary's.
To install latest stock firmware:
Follow the flash instructions and flash the stock ROM. I recommend doing this instead of updating from the phone itself. Because I updated the firmware from the phone itself to the latest firmware using the updater on the phone and there were some small bugs. After flashing everything worked perfectly.
(sorry the links are not clickable, Because I'm a new user with <10 post I can't add clickable links in the threats i create)

I am new to fiddling around android. Would you be able to tell me what's flashing and why do we do it?

elerraoind said:
I am new to fiddling around android. Would you be able to tell me what's flashing and why do we do it?
Click to expand...
Click to collapse
Please use google.
"Flashing a custom ROM" basically means to load a different version of the Android OS. This site actually explains it very well. A custom ROM is the full Android OS customized by the ROM builder usually to make it faster, provide better battery-life or add new features.
AOSP ROMs like CyanogenMod offer stock Android which will remove things like HTC's Sense or Sprint's Apps. CyanogenMod's ROM is one of the more popular ROM.
Other Roms like Fresh 3.5 offer a ROM very similar to the default experience (with added speed and battery-life) by leaving Sense (or whatever skin your device has) and incorporating over the air updates into an updated version of the ROM.
In order to flash a custom ROM you must first root your device. For information about rooting see Matt's comment on the OP or my original answer below:
When I had the same question this is where I found it: .talkandroid.com/7686-what-is-rooting-and-why-should-i-do-it-the-pros-cons-of-android-rooting
Depending on what device you have the rooting method will be different though. Personally I suggest reading up on your device at XDA.
Click to expand...
Click to collapse
Source: android.stackexchange.com/questions/6028/what-is-the-meaning-of-flashing-a-custom-rom

vetkak said:
Please use google.
Source: android.stackexchange.com/questions/6028/what-is-the-meaning-of-flashing-a-custom-rom
Click to expand...
Click to collapse
Appreciate your detailed response. Thanks.

Flashing Problem
Hi, I'm usually quite good at figuring out these problems myself but it has been about two days and still no luck,
I've got a Elephone_P8000_20151203 build, I've been trying the root it as I hate adverts, the problem I get is when I've followed the flashing procedure and enter recovery mode where it gives you the 3 options, every time I press recovery it just loads up the phone, and if I try and enter recovery mode without using flashtools I get no command, I have tried a few different ways now and I don't seem to be getting anywhere so any help would be amazing, I've also tried a different computer OS, I've tried win7/10.
Hope somebody can help,
Regards Chris

xhris1337 said:
Hi, I'm usually quite good at figuring out these problems myself but it has been about two days and still no luck,
I've got a Elephone_P8000_20151203 build, I've been trying the root it as I hate adverts, the problem I get is when I've followed the flashing procedure and enter recovery mode where it gives you the 3 options, every time I press recovery it just loads up the phone, and if I try and enter recovery mode without using flashtools I get no command, I have tried a few different ways now and I don't seem to be getting anywhere so any help would be amazing, I've also tried a different computer OS, I've tried win7/10.
Hope somebody can help,
Regards Chris
Click to expand...
Click to collapse
Have you tried going to settings, enabling developer options, enabling OEM unlocking, then downloading SuperSU from playstore,opening SuperSU, press continue,press normal,this should root your p8000

bjbirch said:
Have you tried going to settings, enabling developer options, enabling OEM unlocking, then downloading SuperSU from playstore,opening SuperSU, press continue,press normal,this should root your p8000
Click to expand...
Click to collapse
Cheers for the reply, I should have mentioned that I tried that also and it still says "there is no SU binary installed, and superSU cannot install it" I found OEM unlocking yesterday and it got my hopes up then shot me straight back down, I was hoping that it OEM unlocking was the reason I could not access recovery,
Thanks again, Chris

To access recovery, switch phone off completely, then press power and volume UP together, you will see three options in tiny white writing,use the volume UP to move marker to recovery which is the first option, then press volume DOWN to choose recovery, you will get a screen with a green android man with a red triangle, you then have to press power and then volume up this should get you into recovery

If recovery is broken. Turn off the phone, connect to PC. Open flashtool. Load philz recovery. Click in download. Turn phone on and flashing should start automaticly. Hope this helps
Verstuurd vanaf mijn Elephone P8000 met Tapatalk

I think it's easier when you use Kingroot for root and Flashify for the recovery

ok sp flash tools wont let me flash just a recovery. It wants me to format and flash the whole phone which wipes out my imei. any suggestions?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

No matter what I try, my computer will not install the drivers. I keep getting "A service installation section in this INF is invalid". Any ideas on what to do?

Nokia N1, wiped system, stuck on splash screen (Powered by Android) (Update!)

Dear Xda,
This is my situation, i had a bootloop so i ran the temporary recovery method explained in the thread "Nokia N1 Rooted with Google Play!" in the general forum of the Nokia N1
But i accidentaly removed the system partition (which boots the system and shows the boot animation etc, after the splash screen)
I can however boot into the bootloader with volume down+power as well as going into the temporary recovery to wipe and flash stuff.
I figured a way to fix this, this is to push or copy a update.zip from my pc (with the original nokia n1 files) to my nokia n1,
but the problem is adb does not recognize this device in the cmd with the command adb devices, and the hardware id is having ???? in device manager (Windows).
Does anyone maybe know a way to push files to this device in either bootloader mode or temporary recovery or maybe another way, as i am stuck with this.
If something is not clear or if i need to post images of my situation of more information please say so,
also i have the taiwanese version not the chinese and i have also all the zip files for android 5.0.1 and 5.1.1 (latest) which 1 of the 2 i need to push to my device to restore the system partition.

Ok, so far i have not gotten an answer from someone,
so i went to look around other forums and identical devices, the closest being the zenphone 2, as they use the same intel processor the intel atom z3580.
I have also looked around alot in the nokia n1 forums on search for the original taiwenese firmware as i have found a way to custom flash the device if it is hard bricked (as in no adb, system or recovery)
I found out that the new intel phone flash tool required a flash.xml file to (re)flash firmwares in order to restore it, so i have been googling around for older phone flash tool programs as i have stumbled upon a nokia n1 thread somewhere where it showed a picture of a custom flash (without the flash.xml file)
I have managed to get a fastboot connection with an old intel phone flash tool program and been trying to flash chinese firmwares to it, but so far it keeps on failing for some reason
I have a feeling that it might be possible to resurrect a broken nokia n1 with the right firmware when you only have access to the fastboot (power up+volume down), we might as well use this method if succesfull to fix bootloops if no recovery is available (as it was with my taiwanese version for some odd reason)
I will attach screenshots of what i have so far, if anyone is interesting in helping me or have an idea please say so.
p.s. i keep on trying to do more research and fiddle more with it, as it cant be more broken than it is now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sadly, i can not go on any further, i have tried and flashed to much files and the nokia bootloader has locked itself, neither does oem unlock commands work with a fastboot flash file, i feel like i was very close to recover the nokia n1, but now it will forever be paperweight, as i have no recovery, no system, no adb, and a locked bootloader so no fastboot anymore.
If anyone have a solution or advise i'm open for this, but until then i can not proceed to test further for people who have like me bricked their device and turned it into useless paperweight (and i feel like the nokia was really vulnerable for bricking) i kinda regret buying the nokia now though.

do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it

2111002640 said:
do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it
Click to expand...
Click to collapse
Yes i do have, do you perhaps know which CN version you had? if not i can attach/link you a CN version.

It is possible to install the same or newer Version of the Firmware, which was installed on your N1
You need a full Firmware package for your tablet (CN or TW Version).
Sent from my N1 using Tapatalk

do you have full ROM for N1 tw or cn, if you have this can you share for me plêas

i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke

2111002640 said:
i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke
Click to expand...
Click to collapse
I don't have a Facebook account. Could you post your solution on here please? Thank you

Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.

srsface said:
Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.
Click to expand...
Click to collapse
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?

defendos said:
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?
Click to expand...
Click to collapse
It's been a week and it was the first time I ever tried to flash anything, but I think that in fastboot I just selected recovery mode with the volume buttons and then pressed the power button to confirm the selection. Since I had previously managed to flash in a recovery image of the Taiwan version, it worked. My saviour was that the recovery image wasn't corrupted even though my Android itself was, so I guess there was no magic trick - I just managed to do the right things finally after wrong physical button presses. If you can't get to recovery then maybe you are truly bricked. Would these suggestions be of any help? forums.oneplus.net/threads/solved-stuck-in-fastboot-bootloader-is-locked-need-help.435522/

same boat bump!
accidently wipe data cant boot stuck on android logo
i can access fastboot but no adb (unauthorize)
on 5.0.2

Question Bricked Pixel 6 Pro Help needed

My pixel 6 pro is stuck in fastboot mode, and for some reason wont boot into android at all. It was running the android 13 beta 2, the device is not rooted, or anything. I have spent the best part of 2 hours navigating through the various bootloader/recovery menus on the phone, but not really getting anywhere. all I was trying to do was unenroll the phone from the beta updates, and return back to stock. it was downloading the latest public build after unenrolling the phone when something happened, and now it doesn't boot.
I am really stuck as I cant use the android flash tool to flash back to the public build of android 12, as I don't have OEM unlocking activated in developer settings on the phone, and obviously not being able to boot into android, means that I cant just restart to enable, like all the guides i have read tell you to do.
Is there a way to flash the phone back to stock android 12 through terminal some how without having OEM unlocking enabled? any help is appreciated, as I am currently looking at a £1000 paperweight at the moment.

There's another software on here called pixel flasher try that if they don't work see of more knowledgeable people message
might have to speak to Google and also were you bought it from
I had the 6 pro put on charge then turned on did restore from back up and it was like 5 to 100 of apps and then it did the march update and it boot looped that was on Saturday
I got into the safeboot mode or whatever it restated as that what I clicked then got into mode again then from there it's froze
I didn't get a replacement till Tuesday lol that was ee had no problems with new one

How about using the android flash tool to reflash the latest beta that you were on?

Also...flashing without a bootloader unlock is like Android No-No ...no.1 ...

TLS993 said:
My pixel 6 pro is stuck in fastboot mode, and for some reason wont boot into android at all. It was running the android 13 beta 2, the device is not rooted, or anything. I have spent the best part of 2 hours navigating through the various bootloader/recovery menus on the phone, but not really getting anywhere. all I was trying to do was unenroll the phone from the beta updates, and return back to stock. it was downloading the latest public build after unenrolling the phone when something happened, and now it doesn't boot.
I am really stuck as I cant use the android flash tool to flash back to the public build of android 12, as I don't have OEM unlocking activated in developer settings on the phone, and obviously not being able to boot into android, means that I cant just restart to enable, like all the guides i have read tell you to do.
Is there a way to flash the phone back to stock android 12 through terminal some how without having OEM unlocking enabled? any help is appreciated, as I am currently looking at a £1000 paperweight at the moment.
Click to expand...
Click to collapse
Since you are able to boot into fastboot, your device isn't bricked and should be recoverable. The first thing you will want to try is booting into Safe Mode to enable OEM unlocking:
1. Press your phone's power button.
2. When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
3. You'll see "Safe mode" at the bottom of your screen.
If that doesn't work, you can also try to flashing the OTA in recovery mode. Lots of videos on YouTube on how to update via OTA in recovery mode. Here's the Android OTA download page - you won't lose your data with this method. Chose the right image.
Next option would be to try wipe or reset by using the Recovery Mode (this will wipe your phone): While in Fastboot/Bootloader, choose Recovery Mode with the Volume buttons. On your screen, “No command” is displayed. Press and hold the Power button. While you hold Power, press the Volume Up button and let go of both buttons quickly. Choose factory reset option (this will wipe your device so be sure to try safe mode and OTA update methods before this option if you are trying not to wipe the phone).
If you just want to get your phone back without trying to save data, try Google's Official Flash Tool. I know most will say it's a waste of time if your BL is locked - but there have been many reports of users fixing issues just like yours even with a locked Bootloader.
Android Flash Tool
flash.android.com
You'll need a Chrome browser.
Because you're on 13 Beta, you could try just reinstalling the Core OS with the web flash Tool. Uncheck all the boxes (don't wipe or re-lock etc).

TLS993 said:
My pixel 6 pro is stuck in fastboot mode, and for some reason wont boot into android at all. It was running the android 13 beta 2, the device is not rooted, or anything. I have spent the best part of 2 hours navigating through the various bootloader/recovery menus on the phone, but not really getting anywhere. all I was trying to do was unenroll the phone from the beta updates, and return back to stock. it was downloading the latest public build after unenrolling the phone when something happened, and now it doesn't boot.
I am really stuck as I cant use the android flash tool to flash back to the public build of android 12, as I don't have OEM unlocking activated in developer settings on the phone, and obviously not being able to boot into android, means that I cant just restart to enable, like all the guides i have read tell you to do.
Is there a way to flash the phone back to stock android 12 through terminal some how without having OEM unlocking enabled? any help is appreciated, as I am currently looking at a £1000 paperweight at the moment.
Click to expand...
Click to collapse
Go back to 13 beta 2 for now. Download the ota onto cpu. Go into fastboot, boot into recovery. Factory wipe in recovery. Then in recovery, go to sideload via adb. Adb sideload the beta zip. You're welcome . Of course you'll have to know how to use adb and all that but hopefully you do.

opz187 said:
Go back to 13 beta 2 for now. Download the ota onto cpu. Go into fastboot, boot into recovery. Factory wipe in recovery. Then in recovery, go to sideload via adb. Adb sideload the beta zip. You're welcome . Of course you'll have to know how to use adb and all that but hopefully you do.
Click to expand...
Click to collapse
Thanks for this, I will give it a go. I have used ADB before, so should be fine with that

Alekos said:
Since you are able to boot into fastboot, your device isn't bricked and should be recoverable. The first thing you will want to try is booting into Safe Mode to enable OEM unlocking:
1. Press your phone's power button.
2. When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
3. You'll see "Safe mode" at the bottom of your screen.
If that doesn't work, you can also try to flashing the OTA in recovery mode. Lots of videos on YouTube on how to update via OTA in recovery mode. Here's the Android OTA download page - you won't lose your data with this method. Chose the right image.
Next option would be to try wipe or reset by using the Recovery Mode (this will wipe your phone): While in Fastboot/Bootloader, choose Recovery Mode with the Volume buttons. On your screen, “No command” is displayed. Press and hold the Power button. While you hold Power, press the Volume Up button and let go of both buttons quickly. Choose factory reset option (this will wipe your device so be sure to try safe mode and OTA update methods before this option if you are trying not to wipe the phone).
If you just want to get your phone back without trying to save data, try Google's Official Flash Tool. I know most will say it's a waste of time if your BL is locked - but there have been many reports of users fixing issues just like yours even with a locked Bootloader.
Android Flash Tool
flash.android.com
You'll need a Chrome browser.
Because you're on 13 Beta, you could try just reinstalling the Core OS with the web flash Tool. Uncheck all the boxes (don't wipe or re-lock etc).
Click to expand...
Click to collapse
Thankyou for the suggestion, my phone however will not boot into any form of android. It just boots straight to the fast boot screen every time. Pressing the power button, you see the Google logo, but it then boots straight to fastboot. It's as if there is no os on the device at all

TLS993 said:
Thankyou for the suggestion, my phone however will not boot into any form of android. It just boots straight to the fast boot screen every time. Pressing the power button, you see the Google logo, but it then boots straight to fastboot. It's as if there is no os on the device at all
Click to expand...
Click to collapse
You mention power button but you never said you held the volume down button as you were powering on. you must hold the volume down button.

TLS993 said:
Thankyou for the suggestion, my phone however will not boot into any form of android. It just boots straight to the fast boot screen every time. Pressing the power button, you see the Google logo, but it then boots straight to fastboot. It's as if there is no os on the device at all
Click to expand...
Click to collapse
I understand it won't boot into Android. Your phone is fine. If you want help, dm me, I will get you sorted. You just need to re-flash Android using the above Flash tool.

Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.
Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!

TLS993 said:
Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.
Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!
Click to expand...
Click to collapse
That's good to hear - it's hard to brick a Pixel.
Best options to resolve issues is the Flash Tool, OTA Update or cli image. The OTA can be tricky when using platforms tools (adb/fastboot).

Hi
I ordered my phone from US, but did not realize that its Verizon OEM locked.
Any Idea how to unlock the bootloader? any way even paid method i am ready.
Now I am on A13 beta which is fine, can I flash a full rom using ADB update without any issues?

anasmhds said:
Hi
I ordered my phone from US, but did not realize that its Verizon OEM locked.
Any Idea how to unlock the bootloader? any way even paid method i am ready.
Now I am on A13 beta which is fine, can I flash a full rom using ADB update without any issues?
Click to expand...
Click to collapse
No Verizon device can ever have its bootloader unlocked. Sorry, you're just out of luck. With a locked bootloader, you can only ever upgrade to other official ROMs, such as Android 13 Beta 3, 4, and final release.

roirraW edor ehT said:
No Verizon device can ever have its bootloader unlocked. Sorry, you're just out of luck. With a locked bootloader, you can only ever upgrade to other official ROMs, such and Android 13 Beta 3, 4, and final release.
Click to expand...
Click to collapse
Thanks for your feedback.... just bad luck

TLS993 said:
Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.
Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!
Click to expand...
Click to collapse
Please how did you do for ADB sideload, because I now have the same problem as you and I'm still stuck on fastboot mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

radioxmen said:
Please how did you do for ADB sideload, because I now have the same problem as you and I'm still stuck on fastboot modeView attachment 5618033
Click to expand...
Click to collapse
Select recovery mode.
When you see No Command, press power and volume up at the same time (quickly). Then try factory reset. If that doesn't work, choose ota update and follow the links above.

Have same exact issue here.
When I try to sideload, I constantly get "cannot read" error.
I tried Large Address Awareness but even that didn't work.
Any help is appreciated

So this tool cant fix your problems?
Android Flash Tool
flash.android.com

No, I keep getting error that OEM is not unlocked