Related
Ok I'm kinda a newbie...I've searched the forums and can't find my solution.
So I installed CM 7 on my nexus one from Rom manager. Everything is ok...so I decide to put google add ons ( froyo). This is what happens now... I get the Cyan logo animation , then the green google sign up logo then the phone reloops to the cyan logo and then the google sign in logo...I cant access nothing on my phone.
I boot into recovery ( power +trackball) , go to recovery option click on power and then I see the X (phone vibrates ) then I get a black screen...and nothing happens.
I did do 2 working rom recoveries from clockwork...I just cannot access them to recover my old working images....Can someone help or did I brick a new phone...
Thanks
just like basketball.......... brick
Maybe try to push a new recovery through ADB?
ok how to do that ADB?
What is ADB ...can someone please help
Thanks
You shouldn't be flashing pre-beta firmwares if you don't know how to use adb.
Use Google or the forum search to find out all about adb.
Also, if the phone is booting as far as the Cyanogen logo, then it's not even remotely "bricked", it does sound like you've managed to stuff up the recovery though, probably ROM Manager's fault, it has a habit of breaking things horribly.
Boot into fastboot and flash the latest Amon Ra recovery, then boot into recovery, do a full data wipe and flash a standard firmware back on.
Yep it's dead, send it to me because I'm building a house.
OK so I fastboot with sdk ...
Because the recovery option just send me to the dreaded X and then nothing
Not bricked. The best people to help you through it the fastest are on the Cyanogen Mod IRC Chat. Make a screenname and one of our amazing Devs will help you though the crisis. Been there, and you'll love them for it.
When I was a newbie in xda, I made sure to research thoroughly before blindly doing weird kinky stuff to my phone.
The xda wiki was one place that helped me in my dark noobish times.
Do yourself a favor and read up the wiki, you might find your answer there.
http://forum.xda-developers.com/wiki/index.php?title=File:Nexus_One.png
get yourself the android SDK, run a cmd window, while your phone is bootlooping;
type adb remount
you should get a message "remount successful"
now type; adb shell rm /system/app/NetworkLocation.apk
and also; adb shell rm /system/app/OneTimeInitializer.apk
your phone should now boot normally
thanks
I.ll try it when i come back from work
But it isn't bootlooping persay...I get the cyan guy and the cm7 logo screen (the arrow turns for awhile...then I get the Green Android guy and it says click to start...I can't even click ...the blue cyan screen starts ...then the green guy ...this loops for ever.
In bootloader mode ( power+trackball) when I try to recover...the the google X logo appears the phone shakes then black screen....nothing happens.
I think that either clockwork recovery is broken (because I saved 3 back-ups from rom manager)...or it works but I cant see screen (SLCD)...Anyway, is there a way to just flash en existing image on my sd card.....
Also my phone was soft rooted (androot) I don't have the big unlocked under the x...will this prevent me from using fast boot to flash???
Thanks guys I know I'm a newbie...Ive read alot...I'm sorry if I offend some of you guys...Thanks for the help....
Sounds like your bootloader is still locked... in that case, fastboot will not work for your phone.
Still read the section on flashing recovery in the xda wiki. There's a section on how to flash a recovery without fastboot but adb.
adB
Ok isn't ADB a driver for usb ...
Anyone know a step by step for morons ( like me)
That have a locked phone, a corrupted bootloader ( or recovery not working) and modified roms on the sd card...
Can i just erase the sd ( put stock image on it)
I will try this at 2pm I must go to work....thanks for the help
Yes.
Download: http://shipped-roms.com/shipped/Pas...le_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
Unzip it, and rename the extracted file passimg.zip
Place it on the root of your SD card and power the phone on holding Vol-
It will find the file and ask if you want to install, pick yes.
Ok
Ok heres what I did so far:
I used an empty sd card ( formated it and put followed what you said: put renamed image oanto sd card)
I power with the volume, here is what happens:
I click on bootloader
I get : recovery option , click the X comes back on shaked and then I get a black screen
Ive waited for 10 minutes nothing
Also: when I click on boot loader, I see ( in green) it saying wrong image, wrong something else.....
Can someone telle what I did wrong
Thanks
Did you extract the zip from within the zip, as instructed?
Sent from my Nexus One using XDA App
ok heres something else I tried:
Went to the original sd card with everything on it) went to the clockwork folder) went to an old back up folder ( copy pasted everything onto the empty sd card) put the sd card into the phone , press power + volume - , get the green guys with skateboards , click onto boot loader ( see the same errors that roll down quickly, funny why they fly down so fast...but I think it says bad image or wrong image or time ) . Anyway, still same thing when I press recover ( with power button) the X shows up , the phones vibrates and then the black screen.
I i do a normal power on ....still get the CM7 boot guy , the arrow that turns around him a few times , then the green guy that ask you to click on him, then you can't even click on him...the CM7 boot guy starts all over (this loops til infinity)
Just so you guys know, the phone was rooted with androot...so I don't know it its still rooted since the software dowsn't work....
Any ideas guys...thanks...
I will try the adb method late tonight...but Im not sure its works if the phone is soft rooted...
Thanks
Did you really rename the passimg.zip correctly? The bootloader should automatically detect the file and prompt you if u want to update. If it did not detect it, it could be the wrong file u renamed.
Remember that once you boot into bootloader using the vol down button, you have to wait for it to detect the passimg.zip before doing anything else.
And fastboot will not work on your phone. You need the roundabout method to flash recovery using cmd.
Ok heres what I did:
1-I download the link Rusty! supplied
2-I extract using winrar to the empty sd card ( a 2 gig card that has been formated using windows format tool to fat 32)..not the one that came with the phone)
3-Once the file in on the sd card, I rename is ( copy paste) exactly passimg.zip
4-I ask windows to eject
5-I insert the card
6-I press the power and volume down
7-I wait , so that fastboot is read.
8-I select fastboot wait a few seconds , select Fastboot ( is green letters) with the power button, it changes to bootloader( green letters), I see green text roll down( says ' i try to see, wrong....something)
9- nothing happens
10-I click recovery, the phone vibrates, get the X, phone goes black
****I tried reading that roll down message : wrong image is there with some other stuff
These are the steps...nothing
Thanks for the help
More info (when I boot in skateboard mode):
nexusone PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0c15
TOUCH PANEL-SYNT0103
my radio is : 5.12.00.08
June 14 2010,12:02:27
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
Its also a videotron phone....I did modify the radio from original stock
Dunno if this can help
Thanks
heei guys .
half a year before I bought the zte blade, and so far it worked well.
but suddenly it stops working ..
whenever I try my cell phone goes immediately to start the red "back" button on (bright red) and then there's the green robot android, then the blue zte intro and then it all over again ..
I have not changed my zte (clockwork, rom)
I know myself well not so good ..
would be really nice if someone could help me ..
I do not know what to do ..!!!
or is it maybe bricked ?!
thanks ..
Its not bricked as it still boots up.
When exactly does the phone crash - when you make a call, start an app, or just automatically reboots?
Did you install a new app just before this started happening?
Is the phone rooted?
Are you sure the battery is ok? Try starting phone with charger plugged in.
ouh ..
yes when i switch the phone on the android boot logo cames then the (blue) zte intro .. and then the zte intro comes again and again ...
noo ..
aahm ? i dont do anything with the pc and the zte ..
so i think i dont root it or something ..
one time there was "ftm" on the screen (after it had this problem).. but i didnt know what this is ..
thank you in front off !!!
but i didnt came anymore to the homescreen , or lock screen
Try booting into recovery and clear the cache? I remember my old G1 did the same thing, and after clearing the system cache it worked.
To boot into recovery i think you keep hold of volume down when turning the device on.
If that doesn't work you could wipe the device, but you'll loose everything on it then.
Sent from my ZTE BLADE using XDA App
The issue you have is this, the rom that has been flashed to the phone is for Gen 2, but the phone is still set on Gen 1.
You'll need to boot into recovery and perform a restore, or flash Ginger stir Fry Rom, then the phone will work.
sent using tapatalk
Solutions depend on
-- whether or not u have custom recovery installed ,
-- whether or not fastboot is enabled in your device. (It isn't enabled only in stock gen2 firmware)
-- whether or not u have rooted and made changes to system partition.
Possible solutions
-- If u have custom recovery installed then format (= wipe data/factory reset) the device from the recovery.
Power off the device. Then by holding volume down power on the device. This takes u into custom recovery menu if it is installed. If custom recovery isn't installed this takes you to FTM MODE.
-- If u have fastboot enabled then use this method to format ur device. Power off the device. Then hold volume up and power on the device. Here the device should stay at green android logo forever if fastboot is enabled. This is fastboot mode. Now install zte USB drivers in PC and connect phone in fastboot mode to PC. It will install the software. Now in device manager u shouldn't see any android named devices with yellow unrecognised format. Then use fastboot windows tools from command prompt. The command to format tthe device is
fastboot erase userdata
-- if the above processes didn't work then using tpt is recommended way. U can flash complete low level device firmware using tpt. U can flash either a recovery alone to hard reset. Or u can flash a complete rom. On bit searching at modaco u will get more information regarding everything.
Sent from my Blade using XDA App
THANK YOU !!
but i dont understand that things .. ?!
can you explain me your answer for people do not understand much of it ?
Download gen1 to gen2 (there is a download link in this section) http://forum.xda-developers.com/showthread.php?t=1258855
Unzip the file and place the image ( the image is called image, not gen1 to gen2) on the root of your sd card (ideally it is best to do this on a pc)
Also download and place the Rom you wish to use on the root of your SD card (cyanogenMod 7.1.0 stable release works well) http://forum.xda-developers.com/showthread.php?t=1297776
DO NOT UNZIP THE ROM at this stage.
Put the SD card back into the phone.
Power off the phone, hold menu & vol + (up) & power at the same time, you should see some green writing, wait until it is finished (well done your phone is now gen2)
You should now arrive at the clockwork recovery screen, if not power off the phone, then hold vol - (down) and power (together), clockwork will boot.
Now using clockwork recovery, clear data/factory reset, then install your rom from the zip, that is all there is to it, obviously you'll have to enter your login details to use the market and sync your contacts etc, but your phone should now be working.
Don't forget to make a nandroid backup.
Goodluck
sent using tapatalk
THANK YOU VERY VERY VERY MUUCHH !!!!
it works perfect !!!!!!!
thanks ((((
You are very welcome
sent using tapatalk
Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much
Hi,
Please help out
Was using your Nexus 4 rootkit.. Everthing was done and phone was rooted .
Now i wanted to update the CWM. I chose the option 11 boot or flash .img files to device. I chose the cwm mako version
and decide to flash it.
Now i am asked options such as boot, bootloader, radio etc.
Here I choose Boot..(This I think I have done wrong.)
Now. Phone only boots to recovery... No matter I with on , Off I cannot go anywhere.. I go directly to CWM.
I tried your toolkit again and this said Phone needs to go in adb .. It says waiting for device..
I cannot also mount the SD card so that i can put some images in the phone...
Hence I cannot do anyhting
Plz help.
Regards
Reflash a rom
Wipe first tho
mark manning said:
Reflash a rom
Wipe first tho
Click to expand...
Click to collapse
How can i flash a rom,When the fact is that i am not able to mount sd card via recovery.
if the nexus had external SD card things would have been easier. I could have just used my SC card reader..
XX-RAZOR-XX said:
How can i flash a rom,When the fact is that i am not able to mount sd card via recovery.
if the nexus had external SD card things would have been easier. I could have just used my SC card reader..
Click to expand...
Click to collapse
Do you not already have one downloaded to the phone?
Sent from my Nexus⁴
mark manning said:
Do you not already have one downloaded to the phone?
Sent from my Nexus⁴
Click to expand...
Click to collapse
No.. I dont have an image on the phone..
XX-RAZOR-XX said:
No.. I dont have an image on the phone..
Click to expand...
Click to collapse
You are going to have to flash the stock image with fastboot. There is a good guide to do so here. Just an FYI this is why you should stay away from toolkits
http://forum.xda-developers.com/showthread.php?t=2010312
Let me know if you can't find the stock image and I'll help you out
Sent from my Nexus⁴
mark manning said:
You are going to have to flash the stock image with fastboot. There is a good guide to do so here. Just an FYI this is why you should stay away from toolkits
http://forum.xda-developers.com/showthread.php?t=2010312
Let me know if you can't find the stock image and I'll help you out
Sent from my Nexus⁴
Click to expand...
Click to collapse
I have a stock image. occam-jop40d
but I cannot go into the bootloader. Pressing that volume keys + power .. The nexus goes out and the red light appears. its not flikering.
XX-RAZOR-XX said:
I have a stock image. occam-jop40d
but I cannot go into the bootloader. Pressing that volume keys + power .. The nexus goes out and the red light appears. its not flikering.
Click to expand...
Click to collapse
I don't know man. With what you have said there is no reason you shouldn't be able to get into your bootloader. If you can't you might be screwed. I flagged your thread in the RC forum. Hopefully some of them will stop by with some other ideas.
Sent from my Nexus⁴
mark manning said:
I don't know man. With what you have said there is no reason you shouldn't be able to get into your bootloader. If you can't you might be screwed. I flagged your thread in the RC forum. Hopefully some of them will stop by with some other ideas.
Sent from my Nexus⁴
Click to expand...
Click to collapse
I am now trying the ADB commads.. in the thread you provided. Lets hope something good comes out..
Till then anyone else can help , will be appreciated.
Can you do
Fastboot flash recovery (name).img
Then fastboot flash boot (boot).img
And then access recovery? If you are in recovery img pretty sure you can use adb. Just a suggestion.
Whatever is in your boot partition (recovery in your case) will be booted when you turn the phone on. This is why you see recovery.
Edit: you cant get into bootloader *at all?* no fastboot then?
Sent with from my Asus Nexus Unicorn
Hi RAZOR, I read your story and it looks like it's not ALL big problems there. I'm willing to help you with that, if you want send me a PM and we talk with GTalk (give you it there), but let's see...
I would plug my cellphone on the PC (hope it works like my Xoom, as they are very similar in some points - Xoom is GED, N4 is Nexus...)
(You said it is booting on recovery), now I would use adb to continue easily...
If you are on Windows:
1 - Open a cmd
2 - cd to adb place
3 - now type adb reboot bootloader, then it would go to fast boot
Now you flash the images you downloaded
On Linux
1 - Open Terminal
2 - Download LAIOT (my tool on signature ) (only to get adb and fast boot ready for use)
3 - Now open terminal and type adb reboot bootloader, then flash the images you downloaded with fastboot
If nothing this work, send me a PM and we'll talk
"This Story Ends Where It Began"
markj338 said:
Can you do
Fastboot flash recovery (name).img
Then fastboot flash boot (boot).img
And then access recovery? If you are in recovery img pretty sure you can use adb. Just a suggestion.
Whatever is in your boot partition (recovery in your case) will be booted when you turn the phone on. This is why you see recovery.
Edit: you cant get into bootloader *at all?* no fastboot then?
Sent with from my Asus Nexus Unicorn
Click to expand...
Click to collapse
Thanks for reply.the first challenge here is actually start the phone. i am not able to start. Read somewhere battery might be depleted. hooked a chafer. its 1 hr but still no start
XxLordxX said:
Hi RAZOR, I read your story and it looks like it's not ALL big problems there. I'm willing to help you with that, if you want send me a PM and we talk with GTalk (give you it there), but let's see...
I would plug my cellphone on the PC (hope it works like my Xoom, as they are very similar in some points - Xoom is GED, N4 is Nexus...)
(You said it is booting on recovery), now I would use adb to continue easily...
If you are on Windows:
1 - Open a cmd
2 - cd to adb place
3 - now type adb reboot bootloader, then it would go to fast boot
Now you flash the images you downloaded
On Linux
1 - Open Terminal
2 - Download LAIOT (my tool on signature ) (only to get adb and fast boot ready for use)
3 - Now open terminal and type adb reboot bootloader, then flash the images you downloaded with fastboot
If nothing this work, send me a PM and we'll talk
"This Story Ends Where It Began"
Click to expand...
Click to collapse
hi ..thanks.. will surely let you know
Not able to start..
Red light comes for a split second and then goes..
Phone is cool even after 3 hrs .. Not to forget.. It cannot even start
XX-RAZOR-XX said:
Not able to start..
Red light comes for a split second and then goes..
Phone is cool even after 3 hrs .. Not to forget.. It cannot even start
Click to expand...
Click to collapse
Not going to lie it is starting to sound pretty grim for you. Keep us informed as to what happens please
Sent from my Nexus⁴
I had a field day this morning with my phone also when trying to flash the stock image back. Finally got it working. The only similarity we had is that I could not mount my data or sdcard either after flashing the stock image.
However, I WAS able to get into fastboot. Should you be able to get into fastboot then RE-LOCK and UN-LOCK your bootloader and everything should work again (fixed my data and sdcard mount issue). I was then able to boot into Android and carry on.
Fastboot oem lock
fastboot oem unluck
Or use the Toolkit.
My only other suggestion would be to take off the back case and try pull the battery (haven't seen it done and not even 100% sure it can be). Maybe the battery just needs a time-out from the phone.
Hope that's some useful information for you.
Good luck.
Well hooking in charger for 6+ hours.. nothing worked...
I think it got screwed
XX-RAZOR-XX said:
Well hooking in charger for 6+ hours.. nothing worked...
I think it got screwed
Click to expand...
Click to collapse
This all still sounds very strange. Wish we could help you get it working but it doesn't look like any of the suggestions have helped. To bad you don't live in the same area as me I'd offer to try and help more.
If you're within the 15 day period perhaps Google can RMA the phone...
asawoszc said:
This all still sounds very strange. Wish we could help you get it working but it doesn't look like any of the suggestions have helped. To bad you don't live in the same area as me I'd offer to try and help more.
If you're within the 15 day period perhaps Google can RMA the phone...
Click to expand...
Click to collapse
And also , adding to this..
I live in India( was shipped here via mail forward sites).. . and 15 days grace is almost over.. (2 days).. even sending it to google from india will take at least 10 days
Try This
Originally Posted by faux123
I got into many red LED situations, I was able to come out of it everytime by using the procedure I posted above (that post was from pure experience I had).
red led bootloop unbrick procedure
1. plug phone into USB cable connected to computer
2. wait for it to go into charge animation
3. unplug, then press power button to boot, immediately press vol up + vol down.
4. hopefully you booted into bootloader mode (rinse and repeat steps 1~4 if you can't get to this point)
5. chose recovery (if your recovery is corrupted, repeat steps 1~4 and do fastboot flash recovery cwmxxx.img)
6. from recovery choose restart system
if you can't get to step 2, because N4 has a bug with battery capacity, plug your phone into AC charge and let it charge for a few mins. then restart from step 1...
Click to expand...
Click to collapse
hi all . so i was on aurora 4.1 . clean install etc and all was fine. then one day phone decided to restart itself. at first it wouldnt boot past samsung logo. then i went into reocvery and changed kernel from h vitamin to ram kernel v1 . and cleared dalvik etc. phone booted fine. then earlier was charging phone at home (official charger) . went ot check phone about 20 mins after and no response. even tried removing battery waiting 10 mins then power on nothing. no vibrate no light. so i realised somehow the phone had hard bricked itself. so started googling about for a solution. found this thread which lets me enter download mode at least. and if i follow the complete guide i can actually boot to setup screen and phone works. only problem is the external sd card only shows 76 mb free as its still partition form before. here is the link for reference http://pastebin(dot)com/7KQxRRNF remove dot and replace with .
right so what i want to know is how do i set boot to emmc so i can actually reformat that sd card so i can use it normally? i tried to install cf root via odin. it flashed fine but when it came to booting phone it wouldnt go past the black screen (that only says kernel in yellow at the top left) . left it on for about 20 mins and it was still on that screen. tried to boot into recovery and it totally messed up and said writing tf flash xxxsectors . then i was only able to boot to that screen no matter what i tried. so had to go reformat card again and re apply steps from that link.
so is there a solution so i can boot my phone normally again then root it and installl custom roms?
im stumped as to why this all even happened as i dont use xposed. and i hadnt changed anything once i installed aurora 4.1 .
phone = n910f .
now bootlooping
now bootloop
after trying to get into recovery it now loops and shows this message
boot recovery mode (in green)
check boot partitions
copy from t-flash
boot recovery
write 54464 sectors..
reboot
even if i remove battery wait put it back in and try boot into download that same set of messages come up and keep looping. anyone know wtf is going on lol
Have you referred this thread: http://forum.xda-developers.com/showthread.php?t=3488114
It also gives the same steps as the paste.bin site.
If you want to repartition your sd card, then you might have to use the EPM.
You can find all that you need, in the thread mentioned above.
Reporting Via N910G
constant looping
yashthemw said:
Have you referred this thread: http://forum.xda-developers.com/showthread.php?t=3488114
It also gives the same steps as the paste.bin site.
If you want to repartition your sd card, then you might have to use the EPM.
You can find all that you need, in the thread mentioned above.
Reporting Via N910G
Click to expand...
Click to collapse
hi thanks. the only problem is that now the phone only shows this message and nothing else no matter what i do.
boot recovery mode (in green)
check boot partitions
copy from t-flash
boot recovery
write 54464 sectors..
reboot
and it keeps rebooting then showing the message again and again.
bump
bump again? please surely someone has a solution . i dont want to move to another phone and then see my note 4 as a paper weight.
?????
dead4ngel said:
?????
Click to expand...
Click to collapse
Try this assuming you can get to Download Mode, credits to https://forum.xda-developers.com/showpost.php?p=70652492&postcount=10