Related
Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
ceevaa said:
Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
Click to expand...
Click to collapse
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
leefear said:
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
Click to expand...
Click to collapse
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
ceevaa said:
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
Click to expand...
Click to collapse
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
leefear said:
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
Click to expand...
Click to collapse
the problem with this is that i first don't have the zip on my phone so cant install from the recovery and second that adb doesnt recognize my phone for whatever reasone so i can't sideload the rom. if anyone experienced similar problems (fastboot working, adb not) please let me know how to fix it
Lukas
another thing i just read about is the possibility if one already has installed a running cyanogenmod rom on his device he can extract that as an system.img if i remember right and i could use it on my hox+. just in case anyone knows how to pull that off let me know =)
otherwise still looking for hints how to install rom via fastboot or how to make adb working again
Lukas
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
ceevaa said:
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
Click to expand...
Click to collapse
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Moynia said:
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Click to expand...
Click to collapse
Hey thanks for the answer
but how do i flash the rom on the phone storage using fastboot?
Lukas
Hi.
I have a problem with my Oneplus X smartphone.
I can't find a similar problem anywhere on the forum.
I've used the MSMdownloadtool 2.0 to recover from a brick. Can go into fastboot and oxygen os recovery but no matter what firmware I try to flash the phone won't boot into anything.
After the oneplus logo it just goes to a black screen and the notification led turns on.
When it is connected to a PC it shows up a 4 separate removable devices.
The bootloader is locked. I can't unlock it because I can't access developer settings because I'm not able to boot into anything.
Does anyone know how to fix this?
Thank you.
s3r3tin said:
Hi.
I have a problem with my Oneplus X smartphone.
I can't find a similar problem anywhere on the forum.
I've used the MSMdownloadtool 2.0 to recover from a brick. Can go into fastboot and oxygen os recovery but no matter what firmware I try to flash the phone won't boot into anything.
After the oneplus logo it just goes to a black screen and the notification led turns on.
When it is connected to a PC it shows up a 4 separate removable devices.
The bootloader is locked. I can't unlock it because I can't access developer settings because I'm not able to boot into anything.
Does anyone know how to fix this?
Thank you.
Click to expand...
Click to collapse
If you have recovery side load may help.or try full unbrick method rather than mini.
Fap4k said:
If you have recovery side load may help.or try full unbrick method rather than mini.
Click to expand...
Click to collapse
i did try that. didn't help either.
I used this guide and worked for me.....
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i did too... didn't work. the Oneplus tech team tried the same thing. Didn't work.
s3r3tin said:
i did too... didn't work. the Oneplus tech team tried the same thing. Didn't work.
Click to expand...
Click to collapse
Same problem here. My device is now in the RMA process and I'm still waiting for their answer if they will repair it on warranty.
They told me that I have voided the warranty because the phone is bricked.
hello, here the same problem.... tried a few TWRP recovery versions but can't access the internal Storage. After the try to flash the phone with the MSMdownloadtool 2.0 (original OP Recovery Flash-Tool) the Oneplus X even boot anymore. No idea what happens with the newest Generation OPX
Date of Manufacture was November 2016?! Perhaps, the problem is the newer OOS 3.xxx. With OOS2.xxx i had no problems to Flash CM13 to a few OPX
Oneplus_X_Flasher said:
hello, here the same problem.... tried a few TWRP recovery versions but can't access the internal Storage. After the try to flash the phone with the MSMdownloadtool 2.0 (original OP Recovery Flash-Tool) the Oneplus X even boot anymore. No idea what happens with the newest Generation OPX
Date of Manufacture was November 2016?! Perhaps, the problem is the newer OOS 3.xxx. With OOS2.xxx i had no problems to Flash CM13 to a few OPX
Click to expand...
Click to collapse
Sorry but with your pseudo, it's a kind of funny
"tried a few TWRP recovery versions but can't access the internal Storage. " what do you mean by that?
Explain what happen at start. OS version, BL state....
Kéno40 said:
Sorry but with your pseudo, it's a kind of funny
"tried a few TWRP recovery versions but can't access the internal Storage. " what do you mean by that?
Explain what happen at start. OS version, BL state....
Click to expand...
Click to collapse
my normal "pseudo" was not available, so i take this funny one XD
Bootloader unlocked, OS --> OOS 3.x. Smartphone had boot into OS.
Recovery cant access internal Storage (Stock Recovery & TWRP)
After the stupid idea using the Oneplus original recovery tool the Smartphone cant boot anymore into the OS.
Now the Bootloader ist locked, cant open him anymore. Stock Recovery & TWRP cant access internal Storage.
OOS 2.x doesn't Boot. Android boot animation doesn't show.
So the main problem was, i want to flash CM13 but cant access the internal Storage (unable to mount data, system etc) wipe, formating, erasing was also not possible. even Fastboot had no access.
After using the "mega unbrick Quide" from Oneplus with the MSNdownload tool @ Qualcomm back door the Smartphone is "bricked"....Fastboot, recovery etc all good, but can't boot the OS (OOS2.x) Bootloader is locked, internal Flash still locked :silly::crying:
Fastboot command are OK?
Whatt's the output of "fastboot devices" &
"fastboot oem device-info"
If you have the old OOS 2 recovery on it, fastboot reflash the OOS recovery then try OOS 2.2.3 full rom zip
Old stuff links here : http://forum.xda-developers.com/showpost.php?p=69170103&postcount=45
If still a problem, and you think the BL is already on the new version, try to fastboot reflash TWRP 3.0.2.1 official and then OOS 3.1.4 with it.
To transfer it, use the microSD card.
After Flashing over the Qualcomm back door, the bootloader ist locked. so fastboot says of course, Bootloader ist locked (Fastboot oem device-info) that means, i cant flash anything by sideload or fastboot codes... and when i try it over the Recovery Boot, recovery is not able to mount /Data /System /cache and so on. so i am not able to flash anything XD Neither cm nor stock oxygen in the version OOS2.x / OOS3.x. I try the old bootloader, the new Bootloader and the TWRP 2.8.x, TWRP 3.0.2.0, TWRP 3.0.2.1, TWRP 3.0.2.2 and the Stock Recovery from CM and OnePlus
I've never had this behavior of a mobile phone The Technical Support Team of ONEPLUS even cant help. very strange. Here someone with the same strange problem... http://forum.xda-developers.com/oneplus-x/help/twrp-access-internal-storage-t3513748
The only way to flash anything to the phone is over the Qaulcomm BackDoor. With the new Bootloader & Kernel of OOS3 the boot animation of OOS3 starts and the phone gets hot. but not boot into the OS. And i can't find anywhere the system.img of OOS3. in the Recovery Tool from OnePlus ist the system.img from OOS2 (I have exchanged single items from directory xxx.img)
sorry it is very difficult to explain this complex problem in english XD
IT from Oneplus tried to flash OnePlus_15_A.11_160420 but it still didn't work. Bootlader is locked so TWRP is not an option or is flashing anything trough fastboot. Only Qualcomm Msmdownload tool or qfil. I've tried the old bootlader, new boolader, h2os, ColorOS, Miui ... but the phone just won't boot into any OS. it stays on a black screen with a white led on and that is it.
if the Qualcomm driver mount you a few partition under Windows, you can flash the internal Storage with an clone of a running OPX. I found an guide how to write direct into the Flash with a PC
Unfortunately I'm from a small town in Croatia. Here I think no one even knows what a Oneplus mobile phone is not to mention owning one... so I am out of luck.
UPDATE: I will get my repaired OPX (or a new one, don't know yet) back tomorrow. They repaired/exchanged it, I had the same problem, black screen and white led. Perhaps my good was to remove the "tampered"-flag from fastboot oem device-info
When I told them I use linux and don't have access to a windows PC they didn't even try the remote-session and told me to send it to them right away.
s3r3tin said:
Unfortunately I'm from a small town in Croatia. Here I think no one even knows what a Oneplus mobile phone is not to mention owning one... so I am out of luck.
Click to expand...
Click to collapse
i have access to two working Oneplus X but the dead phone did not show the removable drive under Windows so i thing we have to send the dead phone back to OP and hope the can fix oder replace it
You should remove the "tampered"-flag before you send it to them. It's simple:
Use the MSMdownloadtool 2.0 to flash twrp (just swap the recovery.img in the MSM-folder). Then you can start the recovery, but I could not do any swipes (screen didn't react), so I couldn't get past the first screen asking if I wanted to mount system r/o. But adb shell was working.
This I used to use the guide at http://forum.xda-developers.com/oneplus-x/help/guide-unlock-bootloader-oneplus-x-using-t3362640
Use adb push/pull to get the file to your pc.
After dd-ing the modified partition back, I used MSMdownloadtool 2.0 to flash the latest original oneplusX-recovery you can download at their site.
I told the support I never rooted the device and was acting like a complete noob, said I had no idea what android version I was on and it seems they accepted it.
It's definitely a hardware problem. Touch isn't working either. The IT guy checked the oem info himself after the flash and after boot was uncussesful and asked me if the phone was rooted. My warranty is now voided. I have decided to sell my oneplus x for parts.
Hi guys
So the phone was working just fine, I wanted to update TWRP and I think I got the wrong image by mistake (I think I downloaded the Mi5 ZCX twrp), flashed it with flashify and when I rebooted nothing shows on the screen, the phone keeps vibrating every 10 seconds and when it's connected to PC I can hear it connecting then disconnecting after 2 seconds when it vibrates, I can't go into recovery nor bootloader, DID I JUST BRICK MY PHONE PERMANENTLY?
Please help guys..
Silvers91 said:
Hi guys
So the phone was working just fine, I wanted to update TWRP and I think I got the wrong image by mistake (I think I downloaded the Mi5 ZCX twrp), flashed it with flashify and when I rebooted nothing shows on the screen, the phone keeps vibrating every 10 seconds and when it's connected to PC I can hear it connecting then disconnecting after 2 seconds when it vibrates, I can't go into recovery nor bootloader, DID I JUST BRICK MY PHONE PERMANENTLY?
Please help guys..
Click to expand...
Click to collapse
What about fastboot mode? And can you link me which twrp you've downloaded?
approach to service center if device is under warranty they will do it for free
prss thanks if i helped
Hi guys
I've fixed the issue using SP flash tool, downloaded the latest MIUI 8.1.7.0 Global Stable for MTK and tried to flash it using SP flash tool, plugged the cable in just after the phone vibrates, the flashing doesn't go all the way but it somehow reset the phone and it booted up to the system with no issues, I re-flashed the correct TWRP for my device and all is good now.
Thank you
Silvers91 said:
Hi guys
I've fixed the issue using SP flash tool, downloaded the latest MIUI 8.1.7.0 Global Stable for MTK and tried to flash it using SP flash tool, plugged the cable in just after the phone vibrates, the flashing doesn't go all the way but it somehow reset the phone and it booted up to the system with no issues, I re-flashed the correct TWRP for my device and all is good now.
Thank you
Click to expand...
Click to collapse
what if he has a SD variant
nikhil020 said:
what if he has a SD variant
Click to expand...
Click to collapse
I honestly have no idea about SD version.
nikhil020 said:
what if he has a SD variant
Click to expand...
Click to collapse
This -
OK -
1. Your device isn't booting, it's just pops up mi logo when we long press Power button.
So, the solution?
I'm telling you one thing that, I don't know about flashing Miui roms, I'll suggest you to flash custom rom, there after you can flash Miui once you gets your device booted successfully.
Now, download these files ~
*. Firmware.zip
*. LineageOS 14.1 latest build
*. Gapps
And Put em' all inside your SD card, Insert your SD Card to your device. Booting into fastboot mode? - Use this combination ~ Power key + volume down.
Then, go to fastboot mode and type fastboot boot <whatevertherecoveryname.img> give it some time, it'll boot to TWRP.
Once you gets twrp, from twrp choose wipe > advanced wipe > wipe everything except internal and SD card > then go back to main menu of twrp choose install» choose downloaded firmware.zip flash it, once it's done, locate unofficial LineageOS rom.zip and let it flash, it done? Then at last choose gapps.zip, flash it.
After this process, hit reboot. [/HIDE]
sachin n said:
This -
OK -
1. Your device isn't booting, it's just pops up mi logo when we long press Power button.
So, the solution?
I'm telling you one thing that, I don't know about flashing Miui roms, I'll suggest you to flash custom rom, there after you can flash Miui once you gets your device booted successfully.
Now, download these files ~
*. Firmware.zip
*. LineageOS 14.1 latest build
*. Gapps
And Put em' all inside your SD card, Insert your SD Card to your device. Booting into fastboot mode? - Use this combination ~ Power key + volume down.
Then, go to fastboot mode and type fastboot boot <whatevertherecoveryname.img> give it some time, it'll boot to TWRP.
Once you gets twrp, from twrp choose wipe > advanced wipe > wipe everything except internal and SD card > then go back to main menu of twrp choose install» choose downloaded firmware.zip flash it, once it's done, locate unofficial LineageOS rom.zip and let it flash, it done? Then at last choose gapps.zip, flash it.
After this process, hit reboot. [/HIDE]
Click to expand...
Click to collapse
Its not my problem neither my question why are u quoting me in the solution ????????
And by the way read his problem again
nikhil020 said:
Its not my problem neither my question why are u quoting me in the solution ??
And by the way read his problem again
Click to expand...
Click to collapse
Eh, you just said '' what if he has an SD version'' right?
So.... That's the workaround for an SD version. Lmao
That's the reason why I quoted you.
Silvers91 said:
Hi guys
I've fixed the issue using SP flash tool, downloaded the latest MIUI 8.1.7.0 Global Stable for MTK and tried to flash it using SP flash tool, plugged the cable in just after the phone vibrates, the flashing doesn't go all the way but it somehow reset the phone and it booted up to the system with no issues, I re-flashed the correct TWRP for my device and all is good now.
Thank you
Click to expand...
Click to collapse
Thanks a lot! Super helpful! [emoji2] [emoji2]
Sent from my Redmi Note 4 using Tapatalk
My device is YU YU4711 , rooted, then I flashed TWRP via fastboot, then using TWRP I backed up the stock ROM , and then flashed RR ROM (7.1.2), it was working fine , but then I thought of flashing RR ROM (6.0) , In the process to do so I couldn't erase the system to flash new ROM (failed to mount system) , so I was on TWRP and I accidentally changed my partition format and since then I have no ROM installed , no internal storage partition , I have TWRP and it shows internal storage (0 mb), I have checked other threads too but found no solution . please please help me .
I'll soon post snaps of the TWRP , and let me know if you need any other information
zap456 said:
My device is YU YU4711 , rooted, then I flashed TWRP via fastboot, then using TWRP I backed up the stock ROM , and then flashed RR ROM (7.1.2), it was working fine , but then I thought of flashing RR ROM (6.0) , In the process to do so I couldn't erase the system to flash new ROM (failed to mount system) , so I was on TWRP and I accidentally changed my partition format and since then I have no ROM installed , no internal storage partition , I have TWRP and it shows internal storage (0 mb), I have checked other threads too but found no solution . please please help me .
Click to expand...
Click to collapse
Hello...!
Try googling "YU YU4711 stock rom". There seem to be enough answers there to your problem.
Most likely you will need:
1. stock firmware
2. Qualcomm USB Driver
3. YU USB Driver
4. Qualcomm Flash Image Loader (QFIL)
Take a look here also!!! https://forum.xda-developers.com/yu-yunique/development/guide-flashing-stock-rom-yu-yunique-t3219897
r&xp said:
Hello...!
Try googling "YU YU4711 stock rom". There seem to be enough answers there to your problem.
Most likely you will need:
1. stock firmware
2. Qualcomm USB Driver
3. YU USB Driver
4. Qualcomm Flash Image Loader (QFIL)
Take a look here also!!! https://forum.xda-developers.com/yu-yunique/development/guide-flashing-stock-rom-yu-yunique-t3219897
Click to expand...
Click to collapse
Thanks for the quick reply , I will download these files asap and flash the firmware , A question , does flashing the stock firmware fixes the partition problem , there are no /internal storage or /data partitions to be mounted .
I had this problem before , it's so simple , learn how to use the ADB SIDE LOAD method so u can push the ROM into the phone storage from PC.
Sent from my VS987 using Tapatalk
zap456 said:
Thanks for the quick reply , I will download these files asap and flash the firmware , A question , does flashing the stock firmware fixes the partition problem , there are no /internal storage or /data partitions to be mounted .
Click to expand...
Click to collapse
To my knowledge, flashing using the QFIL method (and using correct stock firmware) almost completely wipes and repartitions the device to the new (stock firmware). (the correct flashing software is QFIL since your device's processor belongs to the Qualcomm famiy)
You will see pretty soon, if you get on with is, that a scatter file is required for completing the flashing process. If you take a look at the file with a text editor, you might get a better idea of how you device will be partitioned (most likely from scratch).
Look a little bit more around, just to get a better idea on how to use QFIL. There are options on the software to force format/ wipe if nothing else works, or there is also the option to either download or upgrade. You will see once you get the program running.
My concern is that you don't just rush to flash the firmware. Try to understand the process as much as you can, and then give it a go!
r&xp said:
To my knowledge, flashing using the QFIL method (and using correct stock firmware) almost completely wipes and repartitions the device to the new (stock firmware). (the correct flashing software is QFIL since your device's processor belongs to the Qualcomm famiy)
You will see pretty soon, if you get on with is, that a scatter file is required for completing the flashing process. If you take a look at the file with a text editor, you might get a better idea of how you device will be partitioned (most likely from scratch).
Look a little bit more around, just to get a better idea on how to use QFIL. There are options on the software to force format/ wipe if nothing else works, or there is also the option to either download or upgrade. You will see once you get the program running.
My concern is that you don't just rush to flash the firmware. Try to understand the process as much as you can, and then give it a go!
Click to expand...
Click to collapse
I Couldn't connect my phone to the flashing software on the Pc, i followed the guide , but the guide asks to enable usb debugging , which i can't as the phone is off . Nyways thanks for the help .
zap456 said:
I Couldn't connect my phone to the flashing software on the Pc, i followed the guide , but the guide asks to enable usb debugging , which i can't as the phone is off . Nyways thanks for the help .
Click to expand...
Click to collapse
I am not sure if you really need to have enabled usb debugging for this particular method to work. Perhaps more experienced members can chip in here??? Heeeelp!!!!
Still there are a couple of things you can try, provided that you have correctly installed the drivers to enable at least some communication between your phone and the computer.
1. Try just connecting the phone to computer (powered off) after having pressed the download button in QFIL.
2. Try holding the volume up button and connecting the phone to PC (powered off phone) after having pressed the download button in QFIL.
3. Try holding the volume down button and connecting the phone to PC (powered off phone) after having pressed the download button in QFIL.
For all of the above, it would really help if the battery was out of your device (if it is removable).
I really do hope that you will get a chance to revive your device... For the time being, I am out of ideas myself... I wish you the best!
I just rooted my phone lenovo k4 note using golden twrp and flashed resurrection remix with open gapps. Unfortunately the gapps zip file was corrupted and I wasn't able to fix that.
So I booted my phone to the new os , took the new feeling but later realised the gapps are mandatory.
So I downloaded a new file and tried to go to twrp recovery mode. But I wasn't able to. I thought the bootloader must've locked itself up so I unlocked it again, flashed the twrp recovery IMG file with adb and booted my phone to recovery. But still twrp didn't start.
BUT THEN I SAW THAT I HAD NO INTERNAL STORAGE
Just the SD card
Later I was able to wipe the custom rom from twrp and I flashed the resurrection remix and gapps.
Still internal storage was missing. Can anybody help me please?
ParagTheGre8 said:
Later I was able to wipe the custom rom from twrp and I flashed the resurrection remix and gapps.
Still internal storage was missing. Can anybody help me please?
Click to expand...
Click to collapse
Try flashing the stock ROM, see if your storage reappears on your stock ROM.
Also, do you get any information about your internal storage in Settings>Storage on your current ROM?
I don't know if it will help, but in TWRP recovery, go in Advanced>Fix permission
I feel like the OS doesn't have permission to internal storage, in the best case it will fix your issue in the worst case it will do nothing
But safest and easiest way to fix those kinds of issues is to wipe every thing and flash official ROM
Andrew_Geo said:
Try flashing the stock ROM, see if your storage reappears on your stock ROM.
Also, do you get any information about your internal storage in Settings>Storage on your current ROM?
Click to expand...
Click to collapse
Settings>Storage just shows the is size that's is roughly around 7gb
It says 7.11gb used of 7.15gb.
It should have been 16gb
I usually have around 10 GB free internal storage
DevALT said:
I don't know if it will help, but in TWRP recovery, go in Advanced>Fix permission
I feel like the OS doesn't have permission to internal storage, in the best case it will fix your issue in the worst case it will do nothing
But safest and easiest way to fix those kinds of issues is to wipe every thing and flash official ROM
Click to expand...
Click to collapse
So I tried to go to twrp, but the same problem occurred.
It seems my phone is unable to go to recovery.
I did the one with power button and volume keys, and it tries to go to recovery but the ROM boots up.
I also used the is function of reboot to recovery but by this too the ROM boots up and not twrp
ParagTheGre8 said:
So I tried to go to twrp, but the same problem occurred.
It seems my phone is unable to go to recovery.
I did the one with power button and volume keys, and it tries to go to recovery but the ROM boots up.
I also used the is function of reboot to recovery but by this too the ROM boots up and not twrp
Click to expand...
Click to collapse
Ok first of all makes sure ADB is enabled in your settings just in case something goes wrong you will be able to fix it without swearing
Once ADB connect your phone to your PC and use CMD/terminal command to reboot your phone in bootloader
Then reflash TWRP using the CMD/terminal
Once it's done reboot your phone and try to go to the recovery
EDIT: I made some search
And I need you to provide me some more information
RR ROM you flashed, I need the Android version (Lollypop/5.x or Marshmallow/6.x.x or Nougat/7.x.x)
And please provide me the link to the TWRP recovery you used (if you found the TWRP recovery not on XDA, DM me the link instead, follow the rules.)
I might need the phone model/or code if applicable
(Ex: I have a Huawei Nexus 6P but codename is angler) you can see this in the bootloader
EDIT 2: seems like your issue already been answered heads on this thread
https://forum.xda-developers.com/k4-note/how-to/fixed-missing-internal-storage-nougat-t3657798
DevALT said:
Ok first of all makes sure ADB is enabled in your settings just in case something goes wrong you will be able to fix it without swearing
Once ADB connect your phone to your PC and use CMD/terminal command to reboot your phone in bootloader
Then reflash TWRP using the CMD/terminal
Once it's done reboot your phone and try to go to the recovery
EDIT: I made some search
And I need you to provide me some more information
RR ROM you flashed, I need the Android version (Lollypop/5.x or Marshmallow/6.x.x or Nougat/7.x.x)
And please provide me the link to the TWRP recovery you used (if you found the TWRP recovery not on XDA, DM me the link instead, follow the rules.)
I might need the phone model/or code if applicable
(Ex: I have a Huawei Nexus 6P but codename is angler) you can see this in the bootloader
EDIT 2: seems like your issue already been answered heads on this thread
https://forum.xda-developers.com/k4-note/how-to/fixed-missing-internal-storage-nougat-t3657798
Click to expand...
Click to collapse
Thanks for the help but I found what was the concern (my problem is not fully solved)
The recovery was very stubborn to just start up.
So I used the official twrp app and flash booted through my phone.
Fortunately it worked.
I wiped everything including internal storage and the storage just showed up in my pc.
I flashed the ROM and Gapps again and the problem got solved.
There just one thing now, the internal storage is there when I go to Settings>Storage but cant access through File Explorer or pc.
The apps got downloaded to the internal storage only so its not much of a problem though.
I am having the same issue.
DevALT said:
Ok first of all makes sure ADB is enabled in your settings just in case something goes wrong you will be able to fix it without swearing
Once ADB connect your phone to your PC and use CMD/terminal command to reboot your phone in bootloader
Then reflash TWRP using the CMD/terminal
Once it's done reboot your phone and try to go to the recovery
EDIT: I made some search
And I need you to provide me some more information
RR ROM you flashed, I need the Android version (Lollypop/5.x or Marshmallow/6.x.x or Nougat/7.x.x)
And please provide me the link to the TWRP recovery you used (if you found the TWRP recovery not on XDA, DM me the link instead, follow the rules.)
I might need the phone model/or code if applicable
(Ex: I have a Huawei Nexus 6P but codename is angler) you can see this in the bootloader
EDIT 2: seems like your issue already been answered heads on this thread
https://forum.xda-developers.com/k4-note/how-to/fixed-missing-internal-storage-nougat-t3657798
Click to expand...
Click to collapse
I have a huawei Gr5 KII-L21 / kiwi mobile. Initially there was 16GB internal memory now it is just showing 2GB internal memory. I flashed stock rom yet the problem is there. I tried to flash stock rom in bootloader mode from window command prompt. Is there any method to get bak my internal memory?