Hello
I use a ROM with XT897 CM10.2.1 and SIM MOD CornholioGSM since July 2014, it was working fine.
I flashed the ROM-cm-SNAPSHOT-YOG4PAO23E 12.1-20150901-xt897 (RELEASE) one month ago and the ROM worked well. A week ago, the phone was much slower, I turn off reboot and since it constantly!
I made the following transactions with TWRP:
- Reset factory
- Flash ROM (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897)
- Flash ROM (BlissPop-v4.0.1-xt897-OFFICIAL-20150917-1514)
- Flash recovery (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897-recovery.img)
- Flash TWRP
- Flash ROM (cm 12.1-20151007-SNAPSHOT-YOG4PAO339-xt897)
Always the same, I have the boot logo and the logo of the ROM and the phone reboots.
The ROM (CM12.1) has started once and then restart the phone has rebooted repeatedly.
I tried with or without a SIM card.
I do not understand where does the problem, can you help me?
Well not having the phone in front of me, I don't really quite understand the issue myself - however, I would suggest using RSD Lite and one of the FXZ files to flash everything (including recovery) back to stock.
If you still have issues, there is a bigger problem (likely hardware failure).
Hello
sorry if my explanation was not clear.
I added a photo which shows the two steps in the operation of my phone.
Step 1: Start the phone .
Step 2 : boot ROM CM12
The Step 2 lasts 23 seconds then return to Step 1 and Step 2 and Step 1, Step 2 infinitely .
I hope this is understandable .
I read on the forum that used some RSD Lite but as I had not used for the ROM installation, I did not understand why use .
I'm a new user, i can't post picture, I send link by PM, thanks.
I thought my last post made it clear what purpose RSD Lite and the FXZ files are - they restore the phone to stock completely - ROM, recovery, everything will be reset to when it was stock from the factory (granted it may be a newer image than what shipped on the phone, but you get the point).
Again, as I stated previously, if you still have issues after flashing everything stock your issue is likely not software, but hardware.
I searched the forum about RSD Lite. Now I understand its usefulness.
I used RSD Lite to flash the ROM asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip
My phone had with SPRINT .
The flash went well but unfortunately I still have the same problem :
Step 1: unlocked bootloader screen
Step 2: The red M MOTOROLA
Step 1, Step 2 , .....
Is there another test or I can consider it a hardware problem ?
Hardware problem can come out of the MODSIM ? I use a SIM card in the phone for 16 months.
Nicolas.636 said:
I searched the forum about RSD Lite. Now I understand its usefulness.
I used RSD Lite to flash the ROM asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip
My phone had with SPRINT .
The flash went well but unfortunately I still have the same problem :
Step 1: unlocked bootloader screen
Step 2: The red M MOTOROLA
Step 1, Step 2 , .....
Is there another test or I can consider it a hardware problem ?
Hardware problem can come out of the MODSIM ? I use a SIM card in the phone for 16 months.
Click to expand...
Click to collapse
The hardware issue is likely not related to the SIM modification. As to what exactly has failed, I'm not sure... perhaps the NAND or something else memory related.
Aouch aouch...
Thank you for your help.
I think it remains for me to search for a motherboard for photon Q.
Long life in the forum!
Use "borrowed" TWRP recovery image.
Nicolas.636 said:
Hello
I use a ROM with XT897 CM10.2.1 and SIM MOD CornholioGSM since July 2014, it was working fine.
I flashed the ROM-cm-SNAPSHOT-YOG4PAO23E 12.1-20150901-xt897 (RELEASE) one month ago and the ROM worked well. A week ago, the phone was much slower, I turn off reboot and since it constantly!
I made the following transactions with TWRP:
- Reset factory
- Flash ROM (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897)
- Flash ROM (BlissPop-v4.0.1-xt897-OFFICIAL-20150917-1514)
- Flash recovery (cm 12.1-20150901-SNAPSHOT-YOG4PAO23E-xt897-recovery.img)
- Flash TWRP
- Flash ROM (cm 12.1-20151007-SNAPSHOT-YOG4PAO339-xt897)
Always the same, I have the boot logo and the logo of the ROM and the phone reboots.
The ROM (CM12.1) has started once and then restart the phone has rebooted repeatedly.
I tried with or without a SIM card.
I do not understand where does the problem, can you help me?
Click to expand...
Click to collapse
I had a similar incident a few days ago. I have a hard time stopping myself from pushing the limits. Usually I stop when it's broken. I tried RSD Lite, SDB sideload/ flash, zip install from recovery, fastboot(mine's dead), all with no luck.
Any how, If you have CWM, temporarily change to TWRP. If you already have TWRP it's easier.
XDA has a TWRP recovery image in the forum. Put that in your sdcard (I had to paste it from my computer because my xt897 was soft bricked). Flash from TWRP.
Worked fom me. got my phone back after 1 week of flashing everything and then some.
Good luck.
http://forum.xda-developers.com/showthread.php?t=2295643
http://forum.xda-developers.com/showthread.php?t=2295643&page=2
Hello
thank you for this new information.
I tried it and it worked with the ROM [PQ_ICS-Stock] but only with that one!
I tried the ROM [PQ_JB-421] , several Cyanogen ROM but still the same looping boot problem.
I tried several version of TRWP without success .
I do not understand why my Photon Q only works with this ROM [PQ_ICS-Stock] .
Is still a motherboard problem ?
Hello everyone
I'm going crazy !
As I had not managed to solve my problem, I ordered a mainboard on ebay.
Today I realized the SIMMOD on this new board.
when I restarted phone the same startup problems with the ROM SPRINT !
I unlocked the bootloader .
I installed TWRP 2.7.1.2
I installed CM12.1-20151219 - NIGHTLY - XT897
Still the same problem starting loop.
Someone an idea ?
Nicolas.636 said:
Hello everyone
I'm going crazy !
As I had not managed to solve my problem, I ordered a mainboard on ebay.
Today I realized the SIMMOD on this new board.
when I restarted phone the same startup problems with the ROM SPRINT !
I unlocked the bootloader .
I installed TWRP 2.7.1.2
I installed CM12.1-20151219 - NIGHTLY - XT897
Still the same problem starting loop.
Someone an idea ?
Click to expand...
Click to collapse
If you can't RSD Lite, something is up. Either you are not doing the process correctly, or there is something wrong with the device (still).
Perhaps you were always on ICS and never made the official jump to JB? You say you can RSD Lite to an ICS version, just not a JB version? So 4.0.x works but 4.1.x does not?
Again I'm talking stock. If stock doesn't work, I wouldn't even attempt CM. Start with the basics, then work your way towards the aftermarket.
I agree that if the stock rom does not work after the installation with RSD Lite is that it remains something (software) .
The first motherboard I used 12.1 CM for several months it is that the phone supports android 5.1
I agree that it must abort running a stock ROM before flashing a ROM CM. But the ICS ROM STOCK works!
It is possible that I did not do the process correctly .
What surprises me is that the second board had the same problem with the ROM SPRINT !
I will do other tests.
Nicolas.636 said:
What surprises me is that the second board had the same problem with the ROM SPRINT !
Click to expand...
Click to collapse
This is the part that makes me think you are perhaps missing some step in the process somewhere.
Can you RSD Lite to ICS? Not flash it with TWRP. If that is successful, try to RSD Lite to the latest JB again.
I modified the second motherboard ( mod sim card ) and I started the phone with the ROM SPRINT and I got the boot problem repeatedly.
the common point of two motherboards is that they both have a bad ESN .
I will do other tests.
Nicolas.636 said:
I modified the second motherboard ( mod sim card ) and I started the phone with the ROM SPRINT and I got the boot problem repeatedly.
the common point of two motherboards is that they both have a bad ESN .
I will do other tests.
Click to expand...
Click to collapse
Bad ESN shouldn't prevent booting... it would prevent you from activating the device on the Sprint network, but I would imagine you don't care about that...
arrrghhh said:
it would prevent you from activating the device on the Sprint network, but I would imagine you don't care about that...
Click to expand...
Click to collapse
yes
I used RSD Lite 6.1.6 for flashing the ROM [ 2014-03-09 - TSv2 ] but the process has blocked after the flash.
Here is what I did :
1- run RSD Lite
2- Start the phone in FASTBOOT mode.
3- usb phone connection to PC
4- opening of the ROM [ 2014-03-09 - TSv2 ] and "uncompress and start flashing"
5- flash goes well
6- the phone reboots => Logo M red => telephone reboot => Logo M red => again ....
7- RSD Lite waits for the restart ... [ it waits again, LOL ]
8- I turned off the phone and I unplugged.
9- I turned on the phone who start properly, I arrived at the language selection screen .
The ROM is an android version 4.0.4 , I think you know this ROM .
Why the process with RSD Lite has blocked the phone to reboot ?
That's what I did wrong in the process?
I have read many forum post, I tried several methods but only in the ROM 4.0.4 STOCK work. Flashed with RSD lite or restoration of a backup with TWRP.
I have the bootloop problem using RSD Lite 6.2.4 for ROM 4.1.2 CSPIRE or ROM 4.1.2 SPRINT. No error message of RSD lite. No error message of phone.
I've modified the XML file but it changed nothing.
Same problem using TRWP with custom ROM or restoration of a backup ROM4.1.2 JB.
Same problem using OPEN RECOVERY 209 with custom ROM.
Where is the problem ?
I would use CM12 ROM.
Nicolas.636 said:
I have read many forum post, I tried several methods but only in the ROM 4.0.4 STOCK work. Flashed with RSD lite or restoration of a backup with TWRP.
I have the bootloop problem using RSD Lite 6.2.4 for ROM 4.1.2 CSPIRE or ROM 4.1.2 SPRINT. No error message of RSD lite. No error message of phone.
I've modified the XML file but it changed nothing.
Same problem using TRWP with custom ROM or restoration of a backup ROM4.1.2 JB.
Same problem using OPEN RECOVERY 209 with custom ROM.
Where is the problem ?
I would use CM12 ROM.
Click to expand...
Click to collapse
Without having the device in my hands, it's hard to say for sure. The only difference I can see you are doing differently from me is using a newer version of RSD. I doubt that would be an issue, but may want to try other RSD versions.
In the end, I suppose if 4.0.4 works, use that...
Thank you for you help.
I'll buy a other PHOTON Q on EBAY.
I do other test with the new PHOTON Q.
Hello
I received my new q photon.
It is version 4.1.2
I unlocked the bootloader .
I made a backup with TWRP and OPEN_RECOVERY_209 .
I tried an installation of 3 different ROM but I have an error message !
I do not understand where does the problem ?!
Is this a bad version of TWRP or ROM ?
Related
hi i need help i recently downloaded an app called pimp my rom...pretty cool i made some changes and rebooted my phone.. i did this for about 3 time and my phone seemed faster ... but i was tweaking with it and rebooted and i got stuck on the rethink possible screen, so i did i factory reset phone booted up fine ...then i got an error (system ui has stopped working) i clicked ok then got another error (setup has stopped working) now i stuck here.. i have the stock ics file on my computer but i have no custom recovery on my phone so i was wondering if i could flash it using the stock recovery or the pc software... but i don't quite know how to can some one please help me, I'm new to forms
come on guys ... i need my phone for monday
Fxz back to stock.
Sent from my MB865 using Tapatalk 2
Antonoram said:
come on guys ... i need my phone for monday
Click to expand...
Click to collapse
Try using RSD lite and flashing anyone of these ROMs depending upon the region your phone is from
http://sbf.droid-developers.org/edison/list.php (it has the list of all available stock ROMS)
You can find RSD lite on this link http://www.mediafire.com/download/5mvfxv88twuvh34/RSDLite5.7.msi
:laugh:
Hallo Forumianers and XDA-Freaks!
I've got a Samsung Galaxy Note 10.1 (GT-N8010 Wi-Fi only) and I got it two years ago with retail mode software on it. To get this retail s**t off, I flashed it with CWM and installed a custom rom with same functionality as the stock rom. I was happy with it until now. For some reasons I need to get original stock rom on it now (e.g. update capability by Samsung) and here my problem starts:
I downloaded N8010XXUCMA5 - Open Germany - JB 4.1.2 file, extracted the zip and flashed my N8010 with Odin 1.85 and the xxx.tar.md5 file. It worked perfectly until trying to write the boot.img data. At the very last second (actually 1 or 2 seconds before it should have been finished) the procedure failed with a red field in Odin and the word Failed in it.
Then I just tried to restart the device normal and I got the "DEAD-SCREEN" (An issue occurred while updating device... a.s.o.).
Frustrated from hours of work - I tried the same procedure three times with same result - and sleepy I decided to go back to a custom rom for now. So !! I flashed CWM on the N8010 by Odin and made a system restart.... !!!!! I couldn't believe: N8010XXUCMA5 rom started perfectly and works without any problems...
But my main problem stays: I can't use update functionality to update to newest Samsung version...
Does anybody have an idea on how to resolve this problem and just install original stock rom by Samsung? (e.g. resetting binary counter - not yet tried, etc....).
Do I have to do special procedure before installing N8010XXUCMA5 version???
Thank you all in advance for any help and/or ideas!!!
Best regards, Ingmar
AceLine100 said:
Hallo Forumianers and XDA-Freaks!
I've got a Samsung Galaxy Note 10.1 (GT-N8010 Wi-Fi only) and I got it two years ago with retail mode software on it. To get this retail s**t off, I flashed it with CWM and installed a custom rom with same functionality as the stock rom. I was happy with it until now. For some reasons I need to get original stock rom on it now (e.g. update capability by Samsung) and here my problem starts:
I downloaded N8010XXUCMA5 - Open Germany - JB 4.1.2 file, extracted the zip and flashed my N8010 with Odin 1.85 and the xxx.tar.md5 file. It worked perfectly until trying to write the boot.img data. At the very last second (actually 1 or 2 seconds before it should have been finished) the procedure failed with a red field in Odin and the word Failed in it.
Then I just tried to restart the device normal and I got the "DEAD-SCREEN" (An issue occurred while updating device... a.s.o.).
Frustrated from hours of work - I tried the same procedure three times with same result - and sleepy I decided to go back to a custom rom for now. So !! I flashed CWM on the N8010 by Odin and made a system restart.... !!!!! I couldn't believe: N8010XXUCMA5 rom started perfectly and works without any problems...
But my main problem stays: I can't use update functionality to update to newest Samsung version...
Does anybody have an idea on how to resolve this problem and just install original stock rom by Samsung? (e.g. resetting binary counter - not yet tried, etc....).
Do I have to do special procedure before installing N8010XXUCMA5 version???
Thank you all in advance for any help and/or ideas!!!
Best regards, Ingmar
Click to expand...
Click to collapse
Not really know what do you mean about boot.img, but I flashed my note using stock rom dozens of time without any problem, just Odin and the stock 4.1.2 rom.
I was thinking, probably the rom you downloaded was corrupted or something. I would do a factory reset from recovery mode and try flashing other version (older 4.0.2). Then do the upgrade from the settings menu instead. Probably you'll need to upgrade to 4.1.2 first then to 4.4
Resetting binary count works PERFECTLY, using triangle away (props to the dev; chainfire, purchased it immediately). You need to root your device to use it tho. And yest, GT-N80XX is supported (mine is GT N8000, Wifi-GSM).
hope that helps.
cheers
Thank you for your answer.
I tried now four different firmware versions (cma5 to cmk2) also with triangle away before (triangle away -> reset counts and status -> boot to download mode -> flash versions).
Neither of the versions work. The flashing by Odin 1.85 always fails between 20% and 99%.
Why this could hapen??? Does anybody have an idea or suggestion on how to get an official version of JB and recovery on N-8010???
Best regards,
Ingmar
http://samsung-updates.com/device/?id=GT-N8010
They even still keep ICS 4.0.4
Stock recovery :
http://forum.xda-developers.com/showthread.php?t=2102677
cheers
Hey guys,
Have had my Honor 6 H60-L02 FDD-LTE for little under 4 hours now
Already unlocked the bootloader and flashed CWM V.6.0.5.1
I installed the MIUI v4.9.6 Rom and i don't really like it, it keeps coming up saying com.android.phone has stopped, and when you update to v4.12 it gets stuck in a boot loop
So I don't think MIUI is very stable for the phone, and I want to install EMUI v3.0 (This isn't lollipop yet is it?)
Long story short, I figure i have to reflash the stock recovery firmware because CWM wont install an Update.App file
I downloaded the Honor 6 Multitool
When i get to install recovery, i choose my honor 6 model then it asks for EMUI 2.3 or 3.0, i tried all the 3.0's and they dont load the recovery, just go back into android
so i tried some of the EMUI 2.3's, i have no idea what each number at the end represent and which one suits my phone... i.e B118SP02?
So that is what stage im at, i have MIUI v4.9.6 with CWM V.6.0.5.1
And i am trying to install EMUI v3.0 stable
Any help would be pretty awesome, can say im slightly disappointed with the availability of roms for this phone, but hopefully this will change in the future
Ok ...
i will start from beginning , i will tell you how to get the last stable update for your phone .
witch is B310【EMUI3.0_Android4.4】.
First Download it from here it's 1GB .
or from here (you should translate it first and click on stable and download) .
Second continue with this link .
Attention : Do step 6 before 5 .
Or go to
http://forum.xda-developers.com/showpost.php?p=57274153&postcount=1
scroll down to: 3 Button Restore not working (If you change between variant example L02>L12) Or Partition been changes and cannot restore back Stock version. Use this steps below : -
Links to the revert package etc are in the post too
Tried Myahyam's method and now the phone is stuck in a boot loop (shows the honor, powered by android splash, goes black then repeats the splash)
need to unbrick the damn thing now
im following the honor 6 multitools unbrick method, its in fastboot transfering files now, will report back when its done.
Just out of curiosity, besides MIUI and EMUI, what other roms are available to flash using CWM or TWRP?
Okay, managed to get CWM back on and sideload the MIUI4 rom again, just to prove to myself that I didn't brick my phone, so that parts all good!
I will have to try your method another time Julsen, i fly out on a 3 week holiday tomorrow morning, and want to load some games and movies to the phone to watch on the plane.
Hopefully when I come back in 3 weeks, there will be a better choice of roms to install using CWM/TWRK
If not, I will attempt your method Julsen, at least i now know how to fix any softboot/bootloop problems, good learning experience all up!
Here u will find couple of custom roms flashable via cwm
http://bbs.anzhi.com/forum.php?mod=forumdisplay&fid=1387&filter=typeid&typeid=15409&mobile=no
Sent from my H60-L02 using Tapatalk
Help me please!
I am having exactly the same problem that serpent is having.
Did any1 found solution?
Hey all, back from my 3 week trip
@nrpetonr i went to that site and grabbed two roms to flash using CWM, they both seem to put it into a boot loop
This phone is strange really, ever since i have unlocked the bootloader and put on a custom rom, its been the only rom that has worked, the rest all put me into a bootloop
Maybe i should try TWRP instead
Hi,
I flashed the new TWRP2.8.6.0 on my N8000 (before I had 2.8.5.x).
Accidently I flashed the "p4noterf" instead of "n8000" version (with Odin 3.09).
When my SIM-card was not detected, I recognized the error.
Then I flashed TWRP 2.86.0 "n8000"-Version, but SIM was still not recognized.
After that I restored different ROMS (OMNI 5.1; CM12..) from which I had backups, including EFS/IMEI and all other stuff.
Also I wiped (factory, cache, dalvik, system, data) and restored the ROMS again (including EFS...).
But whatever I do: SIM is gone / not detected.
I would be grateful for any help/advice :laugh:!
Me too. I was fiddling with my old 10.1 and decided to give it a run on Lollipop 5.1. I updated the CWM to TWRP and sim recognition was lost. IMEI is blank and mobile network is non existent.
Could any kind soul please advise?
Update: Going back to 4.4.2 stock does show the mobile network signal but there is a notification for SIM card to be inserted. IMEI is back but SIM is still not recognised.
3ftguru said:
Update: Going back to 4.4.2 stock does show the mobile network signal but there is a notification for SIM card to be inserted. IMEI is back but SIM is still not recognised.
Click to expand...
Click to collapse
Perhaps yous can try to restore EFS now (once again) - now that you are back to stock.
There is a thread in a German forum that in 1. step going back to stock saved IMEI. Then, as second step to restore EFS brought SIM back again... Hopefully this helps
Best wishes:good:
Tried using EFS Pro to backup and restore again but it didn't work. Interesting enough, my ROM version stated by EFS Pro is pnote and not N8000. So now downloading and flashing a confirmed N8000 stock rom to see if it works.
Update: Another rom still show p4note which means somewhere in EFS the n8000 is replaced with p4note. Anyone got any idea how to edit back?
3ftguru said:
Update: Another rom still show p4note which means somewhere in EFS the n8000 is replaced with p4note. Anyone got any idea how to edit back?
Click to expand...
Click to collapse
Interesting, indeed.
There's a thread on XDA named "Recover your IMEI in 9 steps". I think it's a description of the problem we are faced with or something very close to, at least.
Unfortunately I am not allowed to post links here :crying: If you PM me I can send it to you.
The logic is the same I found in the German thread: go back to Stock and then change/manipulate EFS.
The crucial file in EFS folder seems to be nv_data.bin perhaps the needed information is in there. There is also a ".bak" and ".md5" of this file.
On my working S3 nv_data.bin changes constantly, date of the file is always "new", not older than a few hours. On the non working N8000 the file date is constant and from early April.
I hope to have some time to explore and test something this weekend .
A further idea might be to (also) go back to n8000 stock recovery - perhaps twrp messed something there.
Again, I can not post the link, just seaarch for the term in www.
Back again!
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
My device type is listed as p4note and not N8000 anymore even after flashing an old 4.1.2 Samsung ROM. Scratching my head on this one.
Anyone knows how to convert back to n8000 for device type?
Same problem. It brokes after installing TWRP.
---------- Post added at 05:47 PM ---------- Previous post was at 05:46 PM ----------
xd_surfer_g said:
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
Click to expand...
Click to collapse
So do you use TWRP at old ROM?
Have found solution:
1. Install stock ROM (older) - sim will be working
2. Install TWRP 2.6.3.1
3. Flash something - and sim will be working, too
CyanoFresh said:
Have found solution:
1. Install stock ROM (older) - sim will be working
2. Install TWRP 2.6.3.1
3. Flash something - and sim will be working, too
Click to expand...
Click to collapse
doesnt work for me whether i got use pit to repartition or just a 4.0.4 stock rom to flash. The SIM just doesnt get recognised.
Guess I just have to use it as a N8010 instead.
3ftguru said:
doesnt work for me whether i got use pit to repartition or just a 4.0.4 stock rom to flash. The SIM just doesnt get recognised.
Guess I just have to use it as a N8010 instead.
Click to expand...
Click to collapse
Try this 4.4.2 rom:
Thread (Ukrainian language) - http://www.ex.ua/91621823
direct download - http://www.ex.ua/load/171252309
torrent - http://www.ex.ua/torrent/171252309
Flash N8000XXUDNH2_N8000OXEDNH1_N8000XXUDNH2_HOME.tar.md5 by Odin. Try to factory reset. it should work
Thank you so much for this thread an especially for this posting!!!
I had the same problem, maybe flashed a wrong recovery/firmware/rom or whatever but I lost access to the SIM card in my N8000. After I follow your steps below now I'm back in stock rom with SIM-access and can reconfigure my tablet.
xd_surfer_g said:
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
Click to expand...
Click to collapse
Tried the Ukrainian ROM but still didn't work.
Now I suspect is that I have accidentally made some changes to the EFS or had damaged the SIM port physically. Otherwise I should have been able to achieve the ROM recognizing the sim card.
Sent from my SM-N910G using Tapatalk
Not working
Sim card comeback after i was reinstall rom 4.4.2, but sim card not working when I install cm12.1 .:crying:
Recovery phone
I thing sim card will working if you recovery phone, file recovery boot with odin:
https:// drive.google.com/file/d/0B_SHfdpTGxm6cHhweGRCR05jYlE/view
After reinstall cm 12.1, 13 for Note 10.1 - N8000.
Good luck.
xd_surfer_g said:
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
Click to expand...
Click to collapse
Hi there, i had flashed cm12.1 for N8000 and didnt backup efs. So even after returning to stock rom, i couldn't find my SIM. My IMEI was lost, and baseband version was showing unknown. So, can I use your method to restore my IMEI and SIM problem? Please reply fast as I need it within a few days. Thank you.
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
BlackSkorpion said:
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
Click to expand...
Click to collapse
You don't give much detail as to what happened or what you were doing prior to your bootlooping. I suffered from a bootloop that took me several months to finally resolve on the very device I'm responding to you with. I was able to resolve it by installing the latest Oxygen OS from the OPO forums. I followed the directions exactly, then after booting into Oxygen it turned out that my WiFi and Bluetooth were refusing to turn on. After several attempts and force close reboots I was able to get them to function. Then I reinstalled TWRP, then flashed CMOS12, then finally CM which I'm using now. BTW for more detail look for my post about it in this forum. Hope this helps.
Odysseus1962 said:
You don't give much detail as to what happened or what you were doing prior to your bootlooping. I suffered from a bootloop that took me several months to finally resolve on the very device I'm responding to you with. I was able to resolve it by installing the latest Oxygen OS from the OPO forums. I followed the directions exactly, then after booting into Oxygen it turned out that my WiFi and Bluetooth were refusing to turn on. After several attempts and force close reboots I was able to get them to function. Then I reinstalled TWRP, then flashed CMOS12, then finally CM which I'm using now. BTW for more detail look for my post about it in this forum. Hope this helps.
Click to expand...
Click to collapse
Hi, i dont know what happened before because the Phone is not mine, is of the gf of a friend. I can reach fastboot and recovery and I also changed the recovery to twrp and installing a new rom, but bootloop still is running. What can i do else?
BlackSkorpion said:
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
Click to expand...
Click to collapse
Do you have a backup? try restoring just the system and the data of your backup.. i used to flash the boot too but as far as i know flashing boot doesn't solve the issue (still bootloop-ing). if you are still in bootloop and really have no idea, try consider a full reset of your phone (all except your custom recovery, ofc) and flash a new flashable.zip rom.. (data+media also wiped) you can always copy files to your phone while in recovery by mounting a usb drive, in case you don't have a zip on your phone. of course, this is not the solution, and is not recommended, but take this as your last choice if any other method didn't work
hope it helps!
Kevin1705 said:
Do you have a backup? try restoring just the system and the data of your backup.. i used to flash the boot too but as far as i know flashing boot doesn't solve the issue (still bootloop-ing). if you are still in bootloop and really have no idea, try consider a full reset of your phone (all except your custom recovery, ofc) and flash a new flashable.zip rom.. (data+media also wiped) you can always copy files to your phone while in recovery by mounting a usb drive, in case you don't have a zip on your phone. of course, this is not the solution, and is not recommended, but take this as your last choice if any other method didn't work
hope it helps!
Click to expand...
Click to collapse
I dont have a backup, so i also tried yet everything you said. I dont have to save datas, so i flashed everything new, but still dont work. I also tried to flash everything from oneplusrecoverytool that in any difficult situations helped me, but in this case it did not worked. Is there any radical solution to get this Phone working? (i can install twrp and reach fastboot, but after installing something, it's always in bootloop. ?
i have the same problem , don't know what to do , i even used the tool to return to stock
maybe an overheat problem? i don't know
Gentlemen, please try the method I suggested above in my response. Go to the OPO forums and follow the procedure to switch to Oxygen OS exactly as they lay out. As long as you're unlocked and can get to the bootloader and recovery you aren't hard-bricked and will be able to eventually fix your handsets. I know from personal experience, because as I mentioned this device was hopelessly stuck in a bootloop for months before I was able to get it running again. Do a search for my previous post for instruction and as I said follow the guide to installing Oxygen to the letter. More than likely you've got several corrupt partitions and this method will resolve it. Once you've got your handset successfully running again on Oxygen you can then begin to flash other ROMs with no issues. For some reason the Oxygen OS is more robust in that it will boot up when there are issues with these corrupted partitions when CM based ROMs won't. I believe the title of my previous post was "hopelessly stuck in bootloop (solved)". I hope this helps.
Odysseus1962 said:
Gentlemen, please try the method I suggested above in my response. Go to the OPO forums and follow the procedure to switch to Oxygen OS exactly as they lay out. As long as you're unlocked and can get to the bootloader and recovery you aren't hard-bricked and will be able to eventually fix your handsets. I know from personal experience, because as I mentioned this device was hopelessly stuck in a bootloop for months before I was able to get it running again. Do a search for my previous post for instruction and as I said follow the guide to installing Oxygen to the letter. More than likely you've got several corrupt partitions and this method will resolve it. Once you've got your handset successfully running again on Oxygen you can then begin to flash other ROMs with no issues. For some reason the Oxygen OS is more robust in that it will boot up when there are issues with these corrupted partitions when CM based ROMs won't. I believe the title of my previous post was "hopelessly stuck in bootloop (solved)". I hope this helps.
Click to expand...
Click to collapse
i tried your solution but nothing changed i also tried this procedure http://forum.xda-developers.com/one...lusrecovery-tool-v1-0-restore-t2991851/page23 , the process is success but at the reboot the phone is always in bootloop
still same problem here =/
Download the latest fastboot image from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471 follow step #8