I need the sctok rom for my zte prestige N9132, please help with this problem.
Rom stock Zte prestige n9132
Hi, Did you get the stock rom of this device? if you did it please give me the information from where you download it, I also having this bootloop problem, Thank you:laugh:
I Need Rom Stock ZTE PRESTIGE N9132 BOOST MOBILE Please.. :crying:
I Need Rom Stock, My ZTE PRESTIGE N9132 Boost Mobile is Bricked, please give me the information from where you download :crying:
Feb. 23, 2017......Please Help
Please help, i have been everywhere on the net and tried every possible method presented. adb, side load, factory reset, wipe/cache. nothing works. rooted my phone, later unrooted because i was gonna take it to be fixed because softkeys stopped workin, but downloaded button savior instead. then eventually wanted mt phone root again. forgot to adb "reboot disemmcwp" first. long story short, bricked phone, stuck at zte logo. i can enter the recovery mode. but it will not allow me to update from sd card for some reason. my usb debugging is not turned on. and most importantly I cannot for the life of me find stock rom or any other rom for this damn phone. as mentioned, i already did factory reset and wiped my data but it did not solve issue. i read in another forum that disabling certain apps could cause a soft brick after doing a factory reset, i did have some apps disabled. so dont know if that is the cause. I know how to flash firmware, roms, and recoveries. But i cannot find a custom rom, or a custom recovery for the ZTE Prestige N9132......so can someone please give me a copy of the stock firmware, or kindly direct me as to where i can download it???? I have scoured the internet for literally 4 days now and cannot find any firmware for this model phone at all......PLEASE HELP!!
6/1/2017 Phone Softbricked
my phone is rooted but last night after it died on me it didn't want to charge it kept turning on and off so this morning I did a hard reset also I charged the physical battery and well after the hard reset it showed
missing bitmap stage_empy
(code-7)
missing bitmap stage_fill
(code-7)
It took a charge and would take me to the setup and then stop at Update Phone and wont go no further.
I already tried live chat with zte and all they want is to pay to get phone repaired
someone help we need the stock rom and I would appreciate it. Thanks
Had mine rooted too and working perfectly, but was trying to replace stock dailer with a custom one. I meant to uninstall the stupid Smart Contacts bloatware and freeze the dailer to see if that caused any problems. But instead I did that backwards by mistake, but I had made backups ... But for some reason couldn't get the backup to reinstall correctly. Titanium was saying the dailer was reinstalled but app crashed at startup. after several attempts I gave up and tried resetting phone to see if that my fix it since it was a default app. Well now I can't get past setup mode. Gets stuck in a loop trying to verify my google account. I also recall after I messed with dailer I couldn't get google to sync contacts, which is why I was so concerned about putting it back. Anyways no stock firmware to be found on net, guess I'm SOL. I think we sould make a post for how to root this phone, b ecause I was a process. And when noobs come looking to see we ask them to get that stack firmware for us before that root. I never did find an easy guide on here just had to search around till I found that piece of adb code that unlocked our bootloader and allowed us to root.
https://androidforums.com/threads/z...ax-and-other-zte-phones.1040331/#post-7317521
Code:
adb reboot disemmcwp
If we can get them to enter the adb code and then copy firmware with adb, would that work? Haven't fooled around with adb to much so I really don't know.
Edit: Just to clarify, I say we should make a new post explaining how to root this phone because the whole time I was searching how to root my prestige never once did this thread come up. If it did, I probably had been able to help those before me and those after me, but to late now... Now I'm in the same boat. Reminds me of the broken soda machine that people keep putting money in all day instead of some one taking time to put a note up warning others to not lose their money too. I'm not that person I now want to help stop other people from making the sames mistakes over and over that seems to be a pattern here.
I found really the only way to root the prestige is with 360 root, not sure if it's actually rooted but I can do everything a rooted phone can but it's only temporary, I have to re root it every time I turn it off or on. 360 is in Japanese but if you download an translation app such as Microsoft translate ( that's better than Google translate in my opinion ) you can pretty easily get your phone rooted. I've used king root and had it rooted for maybe 2 hours then it rebooted by itself and lost it but yeah 360 root in my opinion is the easiest way to root it without a computer.
I found and download firemware on easy-firmware.com/home/browse/category/id/27213/ but phone not seen in fastboot mode, update from sd card not work too. if volume + - and power on phone seen like zte handset diagnostic interface. Please help, how restore this phone?
Here is a stock rom 333770B2622N9132V1.0.0B12
mega.nz/#!avIDVZ5R!8PVq1KloLCyUiwd4kQsS5SrG4XJU0bdZv4F0Wa2KvVk that i found and uploaded there. The phone is set to recovery <3e> N9132V1.0.0B013, but after set this firmware in update from sd card, i get an error:
E: footer is wrong
E: signature verification failed
Fastboot not working, phone is not determined.
Help, how unbrick this device?
---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------
mega.nz/#!avIDVZ5R!8PVq1KloLCyUiwd4kQsS5SrG4XJU0bdZv4F0Wa2KvVk
zte n9132 prestige brick
Am experiencing same thing as you are, i download my n9132 rom from easy-firmware.com, i just cant update it through recovery,i think probably what d cause, is d build number in d recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is not desame as dat of d download file
.
think if i can get a file dat match d bulid number in recovery, it will flash successfully
any solution to unbricking dis device, help guys @allexa1123
---------- Post added at 11:45 AM ---------- Previous post was at 11:42 AM ----------
Am experiencing same thing as you are, i download my n9132 rom from easy-firmware.com, i just cant update it through recovery,i think probably what d cause, is d build number in d recovery
is not desame as dat of d download file
.
think if i can get a file dat match d bulid number in recovery, it will flash successfully
any solution to unbricking dis device, help guys @allexa1123
I think not, because you have N9132V1.0.0B09 but in the downloaded file higher N9132V1.0.0B12 Therefore, it should be updated without replacement, most likely the firmware is broken. Unfortunately I can't restore this phone either. I think you can restore from ZTE Handset Diagnostic Interface(DFU), but how, somebody knows?
do u any any testpoint for dis device @Alexa1123
---------- Post added at 03:03 PM ---------- Previous post was at 02:50 PM ----------
i can actually flash it with NCK dongle or UMT QCFIRE
but it requires the device to be in Edl mode, and i dont have EDL Cable
if i can find any pinout or test point for d device
i will be able to point it in EDL Mode and flash it..
Do have any idea?
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
i can actually flash it with NCK dongle or UMT QCFIRE
but it requires the device to be in Edl mode, and i dont have EDL Cable
if i can find any pinout or test point for d device
i will be able to point it in EDL Mode and flash it..
Do have any idea?
Am still waiting for solution
Sent from my iPhone using Tapatalk
there is no solution in the internet anywhere, phones probably will remain bricks with us) i try to flash qfill with different prog_emmc_firehose_8909 , but have an error
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
в QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
в QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
what do you think, is d problem,
And nobody has even provided us with any solution for [email protected]
---------- Post added at 01:30 PM ---------- Previous post was at 01:28 PM ----------
If there is any way, we can boot the device to EDL Mode
unfortunately, I have not found any solution to this issue either. appealed in support of zte, but they did not give a link to the stock firmware. I'll try again through qfill
ok. please keep me posted
Any solution friend
Sent from my iPhone using Tapatalk
I'm in the same boat. Searched the whole web and just nothing, permanent brick?
Related
htc one x+ bricked how do i unbrick it
help needed.
elithegill said:
htc one x+ bricked how do i unbrick it
help needed.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
elithegill said:
htc one x+ bricked how do i unbrick it
help needed.
Click to expand...
Click to collapse
LLOIR IS BACK EVERYBODY!!! HAHAHAHAHA
Well mate to start off, 90% of the time people mistake bricking the phone for something else. If you can see the screen light up, its not "bricked". Bricking, means that whatever you do you can not fix that phone, meaning you actually can only use it as a "BRICK" as a stone. Who ever made up the word is a genius.
Anyway, Common issues:
Wiped phone no rom [NOT bricked]
Wiped SDCard no rom [NOT bricked]
Broke the screen [NOT bricked]
Phone stuck in bootloop [NOT bricked]
Phone is hot [NOT bricked , Well I honestly can't say for sure since if the phone is waaay too hot it burns your motherboard.. so]
INSERT SOMETHING HERE [NOT bricked]
Well we all have an S-ON bootloader (except the people with the devs phones), so basically you can't brick your phone. Except if you throw it into the water or something.
PrsRep suffre
Ghand0ur said:
LLOIR IS BACK EVERYBODY!!! HAHAHAHAHA
Well mate to start off, 90% of the time people mistake bricking the phone for something else. If you can see the screen light up, its not "bricked". Bricking, means that whatever you do you can not fix that phone, meaning you actually can only use it as a "BRICK" as a stone. Who ever made up the word is a genius.
Anyway, Common issues:
Wiped phone no rom [NOT bricked]
Wiped SDCard no rom [NOT bricked]
Broke the screen [NOT bricked]
Phone stuck in bootloop [NOT bricked]
Phone is hot [NOT bricked , Well I honestly can't say for sure since if the phone is waaay too hot it burns your motherboard.. so]
INSERT SOMETHING HERE [NOT bricked]
Well we all have an S-ON bootloader (except the people with the devs phones), so basically you can't brick your phone. Except if you throw it into the water or something.
Click to expand...
Click to collapse
your above message gives me a hope that I can still use reuse my phone....
basically I have hox+ and rooted my phone on 15th may to install call recorder. have used instruction from this site.
used CWM as recovery and it worked fine till recently when I tried to apply official android 4.2.2 update
after I started getting error mounting sdcard during installation of official update, I flashed CWM recovery and tried different options
and realized that my sdcard has been wiped off.
I do have the backup of "boot.img", "recovery.img", "nandroid.md5" that I took on 15th May as well as the official ROM 4.2.2
but not sure how to get it deployed and make my phone working
current state is that when I restart my phone it shows all network mode , network operators in disabled mode. even Wi-Fi doesn't turn on
while connecting through usb, it just shows my device name as HTC OneX+ and nothing else
if I try to click on the name to view folder details. it says (not responding)
therefore I would need advice from the experts here to enable my HOX+ back in working mode
please help...
just an update here
downloaded sdk 4.3 and tried with ADB command
was able to sideload the zip file to my hox+ but fails with following exception. if someone has faced this issue before please guide
starting ADB sideload feature...
installing '/data/media/sideload.zip'...
checking for MD5 file...
skipping MD5 check: no MD5 file found.
Verifying zip signature...
E:zip signature verification failed: 1
MyHOX said:
your above message gives me a hope that I can still use reuse my phone....
basically I have hox+ and rooted my phone on 15th may to install call recorder. have used instruction from this site.
used CWM as recovery and it worked fine till recently when I tried to apply official android 4.2.2 update
after I started getting error mounting sdcard during installation of official update, I flashed CWM recovery and tried different options
and realized that my sdcard has been wiped off.
I do have the backup of "boot.img", "recovery.img", "nandroid.md5" that I took on 15th May as well as the official ROM 4.2.2
but not sure how to get it deployed and make my phone working
current state is that when I restart my phone it shows all network mode , network operators in disabled mode. even Wi-Fi doesn't turn on
while connecting through usb, it just shows my device name as HTC OneX+ and nothing else
if I try to click on the name to view folder details. it says (not responding)
therefore I would need advice from the experts here to enable my HOX+ back in working mode
please help...
Click to expand...
Click to collapse
---------- Post added at 01:06 PM ---------- Previous post was at 12:21 PM ----------
signature verification can be disabled in TWRP menu under settings....
but now I encounter another problem
E:error executing updater binary in zip''/ata/mdedia/sideload.zip''
not sure if it because of official 4.2.2 release. might be it looks for pre-existing binaries of 4.1.1
will try to download other ROM and try...
MyHOX said:
just an update here
downloaded sdk 4.3 and tried with ADB command
was able to sideload the zip file to my hox+ but fails with following exception. if someone has faced this issue before please guide
starting ADB sideload feature...
installing '/ata/mdedia/sideload.zip'...
checking for MD5 file...
skipping MD5 check: no MD5 file found.
Verifying zip signature...
E:zip signature verification failed: 1
Click to expand...
Click to collapse
hi,
plz help
mine is rooted hox+ devices which is rooted
not able to connect with usb port now, doesn't show anything on my windows file explorer
moreover my mobile shows white screen with htc logo and just hangs
I tried factory reset, even though of no use
I used all-in-ont-tool-kit-2.3
please advice and help to recover my device
Ghand0ur said:
LLOIR IS BACK EVERYBODY!!! HAHAHAHAHA
Well mate to start off, 90% of the time people mistake bricking the phone for something else. If you can see the screen light up, its not "bricked". Bricking, means that whatever you do you can not fix that phone, meaning you actually can only use it as a "BRICK" as a stone. Who ever made up the word is a genius.
Anyway, Common issues:
Wiped phone no rom [NOT bricked]
Wiped SDCard no rom [NOT bricked]
Broke the screen [NOT bricked]
Phone stuck in bootloop [NOT bricked]
Phone is hot [NOT bricked , Well I honestly can't say for sure since if the phone is waaay too hot it burns your motherboard.. so]
INSERT SOMETHING HERE [NOT bricked]
Well we all have an S-ON bootloader (except the people with the devs phones), so basically you can't brick your phone. Except if you throw it into the water or something.
Click to expand...
Click to collapse
MyHOX said:
just an update here
downloaded sdk 4.3 and tried with ADB command
was able to sideload the zip file to my hox+ but fails with following exception. if someone has faced this issue before please guide
starting ADB sideload feature...
installing '/data/media/sideload.zip'...
checking for MD5 file...
skipping MD5 check: no MD5 file found.
Verifying zip signature...
E:zip signature verification failed: 1
---------- Post added at 01:06 PM ---------- Previous post was at 12:21 PM ----------
signature verification can be disabled in TWRP menu under settings....
but now I encounter another problem
E:error executing updater binary in zip''/ata/mdedia/sideload.zip''
not sure if it because of official 4.2.2 release. might be it looks for pre-existing binaries of 4.1.1
will try to download other ROM and try...
Click to expand...
Click to collapse
corrupt download try again. Also try a different usb cable if you have one
Lloir said:
corrupt download try again. Also try a different usb cable if you have one
Click to expand...
Click to collapse
thanks for ur response
now I am stuck in boot looping
and moreover my device is not recognized by windows 7 device manager
tried updating drivers but get code 10 error
seems like I am in loop myself
MyHOX said:
thanks for ur response
now I am stuck in boot looping
and moreover my device is not recognized by windows 7 device manager
tried updating drivers but get code 10 error
seems like I am in loop myself
Click to expand...
Click to collapse
Did you "fastboot flash boot boot.img" ? And you can't use OTA updates of the official rom while being rooted and with an unlocked bootloader as far as i know .
Ghand0ur said:
Did you "fastboot flash boot boot.img" ? And you can't use OTA updates of the official rom while being rooted and with an unlocked bootloader as far as i know .
Click to expand...
Click to collapse
thanks for the note
I did realize that, but now I am desperate to get my phone back in working condition
appreciate any help from experts out here
Hi guys.
I recently bought a BLU Studio G Plus SoC MT6580M Lollipop 5.1.*
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I succesfully rooted this device using King Root and then I used Supersu-me to replace King Root with Supersu.
This is when my device got bricked.
The Supersu-me app showed a message telling me it was succesfull.
However, a second after this message, the phone rebooted and now it is stuck on boot screen.
I dont have a custom recovery so I have to find a workaround.*
Since this model was released on November 2015, there is still no stock Rom on the internet.*
I have a friend that has this same phone and he borrowed me his device to extract the Rom, but I had no luck.*
This is what I've tried:*
1. On my phone I did a Wipe data/Factory Reset and Wipe Cache using the stock recovery but it didnt help, still on bootloop.
2. I did a data backup on my friend's phone using the stock recovery and it was placed on his SD card , then I put his SD on my phone and did a data restore. It didn't help, still on bootloop.
3.Rooted my friend's phone using King Root and installed Busybox. It was successfull. Decided to stay with the King Root app to prevent bricking my friend's phone.
4. I tried MTK Droid Tools to extract the Rom from my friends phone. It says it was complete with errors
(ERROR :No Split Boot Image" - ERROR: Zero file, no space left on device! - ERROR : --- TotalBytesPerChunk Not Found. Set default )
There is plenty of space on the device and SD Card so I dont know what this means. Later I found out that this SoC is not supported yet by MTK Droid Tools
5. Tried editing MTKdroidTools.ini to make this SoC compatible. I managed to create a scatter file to use with SP Flash tools but I had no luck preparing
the previous Rom extracted from my friend's phone to use with SP Flash Tools since it was incomplete/corrupted (not sure).
6. Tried to flash CWM on my friend's phone using MTK Droid Tools but it didn't work (ERROR :No Split Boot Image)
7. Tried installing Philz Recovery and TWRP for MTK on my friend's phone using Easy Magic Istallers with both. Neither worked. It says It was successfull but
when I rebooted to recovery it was the same stock recovery.
8. Tried using MTK Droid Tools on my phone but it hangs in the process of recognizing my phone.
9. I managed to make a Nandroid Backup of my friend's phone using the app called Online Nandroid Backup. It was placed on the SD and then I saved it to my pc.
10. I managed to extract boot.img and recovery.img from my friend's phone using the app called Flashify and saved it to my pc.
So all I have now is My Bricked Phone; a Nandroid Backup taken from my friend's phone; the files boot.img and recovery.img taken from my friend's phone.
I realy need to fix my phone since I bought it to replace my old Blackberry 9360 phone wich no longers meet my work requeriments and right now I cant afford buying another one.
If you need further information please ask. English is not my original language so sorry for gramatical errors.
Any idea would be strongly aprecciated. Thanks in advance.
Any progress?
Any update on your progress? I bricked my Trini Bmobile Blu Studio G Plus in exactly the same way.... kingsroot followed by super sume.
gringobenuk said:
Any update on your progress? I bricked my Trini Bmobile Blu Studio G Plus in exactly the same way.... kingsroot followed by super sume.
Click to expand...
Click to collapse
Hi, gringobenuk.
Yeah my phone is from T&T Bmobile too..
I'm Still waiting.
I found a new tool called SpaceMTKtool wich claims to be similar to MTK Droid Tools and have more compatibility with new MTK SoCs.
http://chinagadgetsreviews.blogspot.com/2015/07/download-spacemtktool-v110.html
I just have to wait that my friend can borrow me his Blu Studio G Plus to make the rom backup using this tool and then flash it in my phone.
If you have access to another Blu Studio G Plus, please try this tool..
I also found this webpage
http://www.clangsm.com/forum/index.php?showtopic=375734
they have all the firmwares for Blu devices including Blu Studio G plus. The problem is that I have to pay 30 USD for a VIP Account in order to download the firmware. I don't even have a Credit Card so there's no chance for me.
If I make any progress I'll let you know. Also If you found something else please let me know.
BTW I'm from Venezuela. Where are you from?
Blu blues
I'm in Trini but from UK.
> I found a new tool called SpaceMTKtool... similar to MTK Droid Tools and have more compatibility with new MTK SoCs.
That sounds like a good find.
> [clangsm.com] have all the firmwares for Blu devices including Blu Studio G plus.
> The problem is that I have to pay 30 USD for a VIP
I found them also. The phone cost 60 USD so not worth spending more on the chance they actually have the right one.
> If I make any progress I'll let you know. Also If you found something else please let me know.
Will do. I have learned that the D790 roms are not the correct roms and that there are two versions of the STUDIO G PLUS ... the S500Q and the S510Q (I do not know the difference)
PS. Did you manage to get yours unlocked and if so, how?
You have been doing bad!
You are doing everything wrong. I can see you aren't familiar with how the phone works. Don't worry, just follow instructions and you will probably have your phone back.
This is the thread you need, everything you need:
http://forum.xda-developers.com/showthread.php?t=2160490
"NEVER EVER FLASH THE PRELOADER" you will be fine otherwise
You will be using this tool: SP_Flash_Tool_exe_Windows_v5.1452.00.000
in addition to the other one you know (MTK tools)
Flashing CWM takes like 5 minutes when you know what you are doing, but like 1 hour reading that post I gave you the first time. (That guru posted the same in russian, in case you can understand that one better)
The resume would be
1) Make scatter file with MTK tools AND a working phone
2) Use scatter in SP flash tools to extract Boot image (recovery) from working phone
3) Use MTK tools to generate a "compatible" CWM
4) Flash that CWM using SP flash tools to bricked phone
Now you have cwm. If it works on the bricked phone, you must do the same on the good phone
5) Flash CWM the way you just learned on the good phone
6) Use MTK tools to make a backup of the good phone
7) Restore the good phone's backup made by MTK tools using SP flashtolls on the other phone
SP flash tools works with the phone "turned on" and, while connected, turning it off when you are ready to start. Thrifty, eh?
You can't restore backups made by sp flash tools on these phones.
once you have CWM, you can flash supersu with another method, because MTK is not rooting my phone correctly.
if you are using MTK tools with these phones differently, you are not doing it right.
Look at the pictures at the end of this post, our phones have three screens
1) stock recovery (volume up)
2) Factory tests (volume down)
3) Fastboot (I can't enter this with keys, only with commands, if you discover how, please post)
==================================
I wonder If the lollipop could be ported to my phone. When you unbrick one, please post the SP Flash tools and the scatter file, will you? Thanks.
If you check this page, it is the BLU Product page for both our phones
http://bluproducts.com/index.php/studio-g-plus
http://bluproducts.com/index.php/studio-g
and
Check Mediatek's site (the one making the boards)
http://www.mediatek.com/en/products/mobile-communications/smartphone1/mt6582/
Our phones use the same board
These phones seem good quality, but the company (BLU) has poor quality control. So, bad phones make it into to stores. I bet your phone's memory is corrupted, but you won't have an easy time demonstrating it. Best bet is trying to exchange it for a new one.
It took me 5 minutes to find your stock room
https://clangsm.com/ftpdemo/index.php?dir=Flashes/BLU/Studio G Plus/
The problem is it is not free.
You can still extract your friend's phone system as stated. Please upload it once you retrieve your own phone!
make backup of good studio g plus with scatter file via infinity mtk or other tool and flash bricked one with sptools.
---------- Post added at 09:06 AM ---------- Previous post was at 09:00 AM ----------
need s500q 02 rom backup mt6580, i have s500q but not the 02 version, flashing it to the 02 version will make display white, but everything else still works.
mr64fixit said:
make backup of good studio g plus with scatter file via infinity mtk or other tool and flash bricked one with sptools.
---------- Post added at 09:06 AM ---------- Previous post was at 09:00 AM ----------
need s500q 02 rom backup mt6580, i have s500q but not the 02 version, flashing it to the 02 version will make display white, but everything else still works.
Click to expand...
Click to collapse
thats correct..and the thing is i changed motherboard and display is still white!!!!i have a next model and as i was about to take a backup..thats when this one is stuck on logo!!!!any help would be highly appreciated!!1
need recovery ... custom or stock for studio g plus S510 v10 generic
i lost my recovery for my studio g plus and need to flash one for this phone. available for the studio g but not plus. any help would be greatly appreciated
I have the same phone from Bmobile. I have the 02 version and I am unable to find the stock rom for it.
Who want stock ROM so click: Stock ROM G+ from William Smith or BLU Development Team G+
Who want be a tester for Custom Recoveries so PM me!
Hey guys , i m trying to root the OUKITEL K6000 PRO but i cant make it. I 've searched in the net a lot, used (i think) all the tutorials (kingoroot, rootgenius, towelroot, rootkhp, android_root) but still i cant root it. If anyone has a hint i would appreciate it a lot, thanks for your time
How To ROOT
Please contact me I'll teach you, I posted a tutorial but the xda forum prevents me to send you the download links, [email protected]
Hello! I'm having problems to do root in my k6000 pro. Any news about this?
Hi there, any update on this?
Any update on this?
I need to know this as well. Can some one help. Found something here but it is in spanish:
http://www.movilesdualsim.com/tema/supersu-k6000-pro.140140/#post-1580954
Can someone translate it please if this is valid?
Found a french guide if anyone care to translate and post here please:
http://www.phonandroid.com/forum/ouiktel-k6000-pro-android-6-3g-ram-32g-avec-su-et-twrp-t151298.html
Okay I found this English guide and I have successfully install TWRP and Chainfire root.
I have followed this article and it works.
http://www.needrom.com/download/twrp-3-0-2-1-k6000-pro/
This is specs of Oukitel K6000 Pro:
SoC: MediaTek6753
CPU: MTK6753 Octa Core 1.3GHz
Build Number: OUKITEL_K6000_Pro_V8.0_20160607
Here is the screenshot from sp flash tool during the download process of TWRP to phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
See the root status:
Root OK
Xposed OK
TWRP OK
And now an official x64 rom and also the 1st custom rom xOS appeared a few days ago.
hi everybody i have maked a mistake to root oukitel k6000pro...i have opened the flash tool...i added the scatter ....clicked Download...all good....and then....i'm going to open the phone and is not opening....i'm very crazy for this (( what can i do...please help meee !!!!!!!!!!!!!!!!!!
My phone has damaged after fashing the TWRP the device doesn't reboot
hello! my phone Oukitel K6000 pro how TWRP and Root please tell kind of TWRP version& root step by step Thank you.....
Hi friends,
I have few question :
1. know anyone what is difference between Clasics ROM and FZ ROM (newer phones coming with FZ ROM)
OUKITEL K6000 Pro FZ V11 20161119
OUKITEL K6000 Pro ROM V9.0 - 2016.09.24
2. I install FZ ROM to my phone with Clasics ROM without problem phone is working.
3. NEW phone: In android recovery mode is test "Root Integrity Check" Every time if i run this test i receive message
"Error: found 9 new files / System chceck FAIL!!" same error with original Clasic ROM and same error with FZ ROM
Thank You
Guys, this can be solved. If you have the mediatek drivers correctly installed, and then the driver signature deactivated (follow this tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/ ).
Download firmware with scatter file from here: .needrom.com/download/oukitel-k6000-pro-v12/
TURN OFF THE PHONE (make sure is no background light, some times when the phone is dead ocurre this when pressing power botton)
After that use sp flash tool, Load scatter file and in the Format tab mark Validation, Autoformat flash and Format whole flash
conect the phone to the usb
Disconect the phone
On the Download tab, select Format all+Download
And this is it! OUKITEL K6000 PRO come back to live
Sorry for my strange english
One more thing, you will lose your imei,and there is no CDS option to change it.
You need to root the phone to asign an imei.
---------- Post added at 01:02 AM ---------- Previous post was at 12:48 AM ----------
babardy said:
My phone has damaged after fashing the TWRP the device doesn't reboot
Click to expand...
Click to collapse
Guys, this can be solved. If you have the mediatek drivers correctly installed, and then the driver signature deactivated (follow this tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/ ).
Download firmware with scatter file from here: needrom.com/download/oukitel-k6000-pro-v12/
TURN OFF THE PHONE (make sure is no background light, some times when the phone is dead ocurre this when pressing power botton)
After that use sp flash tool, Load scatter file from downloaded folder, and in the Format tab mark Validation, Autoformat flash and Format whole flash and click start
connect the phone to the usb
wait to finish (ok messege)
Disconnect the phone
On the Download tab, select Format all+Download and click Download
Connect the phone to the usb
what to finish (ok messege)
disconnect and power on
And this is it! OUKITEL K6000 PRO come back to live
Sorry for my strange english
One more thing, you will lose your imei,and there is no CDS option to change it.
You need to root the phone to asign an imei.
oukitelk6000 said:
Guys, this can be solved. If you have the mediatek drivers correctly installed, and then the driver signature deactivated (follow this tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/ ).
Download firmware with scatter file from here: .needrom.com/download/oukitel-k6000-pro-v12/
TURN OFF THE PHONE (make sure is no background light, some times when the phone is dead ocurre this when pressing power botton)
After that use sp flash tool, Load scatter file and in the Format tab mark Validation, Autoformat flash and Format whole flash
conect the phone to the usb
Disconect the phone
On the Download tab, select Format all+Download
And this is it! OUKITEL K6000 PRO come back to live
Sorry for my strange english
One more thing, you will lose your imei,and there is no CDS option to change it.
You need to root the phone to asign an imei.
---------- Post added at 01:02 AM ---------- Previous post was at 12:48 AM ----------
Guys, this can be solved. If you have the mediatek drivers correctly installed, and then the driver signature deactivated (follow this tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/ ).
Download firmware with scatter file from here: needrom.com/download/oukitel-k6000-pro-v12/
TURN OFF THE PHONE (make sure is no background light, some times when the phone is dead ocurre this when pressing power botton)
After that use sp flash tool, Load scatter file from downloaded folder, and in the Format tab mark Validation, Autoformat flash and Format whole flash and click start
connect the phone to the usb
wait to finish (ok messege)
Disconnect the phone
On the Download tab, select Format all+Download and click Download
Connect the phone to the usb
what to finish (ok messege)
disconnect and power on
And this is it! OUKITEL K6000 PRO come back to live
Sorry for my strange english
One more thing, you will lose your imei,and there is no CDS option to change it.
You need to root the phone to asign an imei.
Click to expand...
Click to collapse
You are my hero, i have trying to fix my phone for hours and your description is perfect, thank you so much :highfive:
As there is no sub-form for this phone, I am going to piggyback off of this due to the keywords and such... But.. Does anyone have issues with getting anything more than EDGE network from within the USA? Namely TMobile. I checked the freq's the phone and TMO uses and most match up with a few missing on the LTE side, but utilizing one at least... But I have not been able to get anything past EDGE connection, and that won't even pull web pages... Any ideas?
And there is a way to root the new k6000 plus?
Truzzman2 said:
And there is a way to root the new k6000 plus?
Click to expand...
Click to collapse
wrong thread
Okitel k 6000 pro os
Greetings!
What would be safe to use to unlock root access for
OUKITEL_K6000_Pro_FZ_V12_20161129_211434
?
There doesn't seem to be anything specifically for this version at...
https://www.needrom.com/category/oukitel/k6000-pro/
-- There are releases for somewhat earlier or later versions. Releases with more positive feedback and ratings are not chronologically the closest to '20161129_211434' available.
Thank you in advance!
All the best!
It is a fairly new device so I haven't seen anything on it but I'm hoping someone could point my in the right direction. Any info would be helpful. Thanks!
Same here, looking for root!
Coolpad root
Good luck on this to you I am working as well and will post what I find
Picked up one of these today, we just started working on it a few minutes ago, I'll post the method once done. This could be hours, days, months, who knows, We do have fastboot and the Coolpad Kit from elsewhere on the forums so it shouldn't be hard. But we are working on it.
Same here I really want root, oddly for fastboot oem unlock it doesn't unlock , I have oem unlock enabled in developer options but when I run the command fastboot flashing unlock or fastboot oem unlock or pretty much any command besides fastboot getvar all it comes back with something like FAILED remote unknown command and I have no idea why I have the cool pad legacy/lithium cp3705a if anyone can lend me some knowledge on why the fastboot commands don't work that would be nice I was going to flash a gsi and try to patch a stock boot image via magisk but I can do anything without unlocking the bootloader first, I'm hoping it's not a kernel related issue
sawclan22 said:
Same here I really want root, oddly for fastboot oem unlock it doesn't unlock , I have oem unlock enabled in developer options but when I run the command fastboot flashing unlock or fastboot oem unlock or pretty much any command besides fastboot getvar all it comes back with something like FAILED remote unknown command and I have no idea why I have the cool pad legacy/lithium cp3705a if anyone can lend me some knowledge on why the fastboot commands don't work that would be nice I was going to flash a gsi and try to patch a stock boot image via magisk but I can do anything without unlocking the bootloader first, I'm hoping it's not a kernel related issue
Click to expand...
Click to collapse
Yeah still working on it, waiting for some pie PoCs to come out. But fastboot is borked. I've requested the source code from them we'll see how that goes, doubt it will go anywhere. Can't even find the proper drivers for it. MTKTool is outdated so it can't even get a read on the FS to make a scatter file. All one click apps I tried didn't work so I wouldn't recommend those. OneClickRoot said it could root it but I'm not about to pay them to find out.
I did find a binary(locksettings) in system that allows you to set and remove passwords via command line which seems a bit insecure, but possibly exploitable, and an empty "cdrom_install.iso" in /system/etc But It just says:
"This directory contains the raw data that OEMs want to expose
to end-users.
Due to the limitation of mass storage. The cdrom ISO file should
be larger than 600KBytes.
If you put less files into this directory. Then it will create
a dummy file to fill the gap."
With a nice 616KB pad file.
That's all I've been able to get so far.
Thanks for the update that sums up what I've got as well although i didn't see that system img
---------- Post added at 03:51 AM ---------- Previous post was at 03:47 AM ----------
Oddly my device seems to be having some sort of bug. The touchscreen will just randomly lock up , I've reset the device , I realized it doesn't so it in safe mode , so I tried deleted apps from adb shell that did nothing , but since it works in safe mode and the device has project treble support I feel as though flashing a gsi would fix the problem , but I can't so that with a locked bootloader
sawclan22 said:
Thanks for the update that sums up what I've got as well although i didn't see that system img
---------- Post added at 03:51 AM ---------- Previous post was at 03:47 AM ----------
Oddly my device seems to be having some sort of bug. The touchscreen will just randomly lock up , I've reset the device , I realized it doesn't so it in safe mode , so I tried deleted apps from adb shell that did nothing , but since it works in safe mode and the device has project treble support I feel as though flashing a gsi would fix the problem , but I can't so that with a locked bootloader
Click to expand...
Click to collapse
You might want to go through your apps and disable a bunch of the bloat. They had like 3 facebook managers, installers and stuff in there. That could be doing it. I haven't had any such issues but i've only had the phone a few hours and have been in a shell exploring it most of that time.
Update: EDL Mode is accessible. We haven't been able to successfully do anything with it yet due to lack of a firehose, but 9008 mode does work with EDL Cable. If anyone has a SDM450 firehose around that would be ideal.
I already noticed edl mode was there was planning on finding out what to do today , I have a firehouse for the board which is prog_emmc_firehose_8953_ddr.mbn , but I wasn't sure how that worked I'm not to familiar with edl mode or what it can do , also I'm not a dev just an experienced Android / Linux user
---------- Post added at 01:32 PM ---------- Previous post was at 01:30 PM ----------
What would u even use to flash in edl mode? Say a gsi , because there's no stock firmware we can extract , but we can always get a rooted gsi if I'm not mistaken because the device does have project treble support
Sapphiress said:
You might want to go through your apps and disable a bunch of the bloat. They had like 3 facebook managers, installers and stuff in there. That could be doing it. I haven't had any such issues but i've only had the phone a few hours and have been in a shell exploring it most of that time.
Update: EDL Mode is accessible. We haven't been able to successfully do anything with it yet due to lack of a firehose, but 9008 mode does work with EDL Cable. If anyone has a SDM450 firehose around that would be ideal.
Click to expand...
Click to collapse
The firehouse for the oppo a71 has same specs board RAM and soc would that work
sawclan22 said:
The firehouse for the oppo a71 has same specs board RAM and soc would that work
Click to expand...
Click to collapse
I'll see if I can find one. They have the board incorrectly listed as both an MTK board and as an msm8953 even though from what I've been able to find msm8953 is strictly the snapdragon625. And Snapdragon 450 doesn't have an msm designation. This thing is a mess inside.
It's been awhile since I've done this mind you. Android has changed a bunch since the 2.X and 4.X days. I've been on a Nexus 6P for years which is open by default.
Wish it was as easy as installing gingerbreak and tapping root like the old days. Lol
---------- Post added at 03:14 PM ---------- Previous post was at 03:03 PM ----------
sawclan22 said:
What would u even use to flash in edl mode? Say a gsi , because there's no stock firmware we can extract , but we can always get a rooted gsi if I'm not mistaken because the device does have project treble support
Click to expand...
Click to collapse
I would get temp root via a RCE or EoP pull the boot image, modify it and flash it in EDL therefore enabling fastboot and making the phone ready for TWRP. After that it's just a matter of writing a program that does this for you and the phone would be ready for development.
Well I've done all I know how to do I'll just leave it to you guys and keep an eye on this forum
Hey Sapphires,
Have you generated the root process for the Coolpad Legacy yet?
[email protected]
manoftech said:
Hey Sapphires,
Have you generated the root process for the Coolpad Legacy yet?
[email protected]
Click to expand...
Click to collapse
Waiting for a poc or a firehouse to surface. Android 9 doesn't have many exploits available yet.
Device Unlocking Process Status?
Have we got anywhere with the device unlocking and rooting procedure with this device.
djdruin said:
It is a fairly new device so I haven't seen anything on it but I'm hoping someone could point my in the right direction. Any info would be helpful. Thanks!
Click to expand...
Click to collapse
dravenz7 said:
Have we got anywhere with the device unlocking and rooting procedure with this device.
Click to expand...
Click to collapse
Nope. we are also NOT vulnerable to CVE-2019-2215 at least on my device with the June Patch. Just waiting for a valid exploit.
This is as far as it gets.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You guys suck
diag port
I don't know if you guys figured this part out yet or not but I was able to open the engineering menu and turn on the diagnostics port and modem. I'm not very familiar with using it to my advantage but I used quick shortcut maker to open it. It was under yulong labtest I believe. One of the menus are all in chinese so I'm not real sure what else it would let you access.
TreyVega said:
You guys suck
Click to expand...
Click to collapse
Well let's see you do something there buddy, obviously you're the expert on the subject.
Cracking enterprise level security isn't just clicking a button. and you ain't paying me. I have a stack of phones and other devices to work on and other more pressing things to do with my life. So, kindly, take your opinion and shove it, root will be released when it's released.
m3nty said:
I don't know if you guys figured this part out yet or not but I was able to open the engineering menu and turn on the diagnostics port and modem. I'm not very familiar with using it to my advantage but I used quick shortcut maker to open it. It was under yulong labtest I believe. One of the menus are all in chinese so I'm not real sure what else it would let you access.
Click to expand...
Click to collapse
EDL mode won't help without the proper mbn, none of which that are publicly available work. Or if you're talking about the hidden flasher activity we found that awhile ago but I haven't really looked too far into it as i don't have a USB-C OTG drive.
Hello,
my GFs phone with Lineage OS started to bootloop randomly yesterday so I have tried to reflash it witch does not worked. Everytime I have booted into recovery twrp was unable to mount storage so I found some tutorials whose suggested to change filesystem or repair it but none of them worked. As a last resort there was unlocking bootloader but now I cant unlock it after locking because I cant access system and phone is not associated with my account anymore. Is there any way to fix this? Thanks in advance
try clean flashing a fastboot global stable rom using mi flash tool(dont forget to choose clean all in the pc flash tool).
Thanks for your reply, I have tried MiFlash app but I am getting error "Erase boot error"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
put your phone in fastboot mode.request anther unlock code if that dont work create new account on pc try again might work then you could use flash tool
Unlocking even with new account does not work because I am unable to link my phone to MI account
there is way with locked bootloader look up EDL mode on youtube you have to take phone apart or shop might fix it that way for you.
---------- Post added at 04:20 PM ---------- Previous post was at 03:57 PM ----------
here read up on edl mode
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
Aealo said:
Hello,
my GFs phone with Lineage OS started to bootloop randomly yesterday so I have tried to reflash it witch does not worked. Everytime I have booted into recovery twrp was unable to mount storage so I found some tutorials whose suggested to change filesystem or repair it but none of them worked. As a last resort there was unlocking bootloader but now I cant unlock it after locking because I cant access system and phone is not associated with my account anymore. Is there any way to fix this? Thanks in advance
Click to expand...
Click to collapse
You need a windows pc for this method.
Download latest miui recovery rom from here.
http://bigota.d.miui.com/V10.3.6.0.PEJMIXM/miui_POCOF1Global_V10.3.6.0.PEJMIXM_0ba4120b12_9.0.zip
Rename it to stockrom.zip and save to desktop of pc
Reboot phone to recovery. Select mi assistant.
Install google adb drivers and download platform tools from here. http://goo.gl/zTGVyM (32 bit)
http://goo.gl/el03X5 (64 bit)
run command from pc(cmd)
Adb devices
Now if u see any device showing sideload .you have successfully installed adb drivers. If not, search more on xda for adb installation.
Now this if your device appear in list.
adb sideload <path_to_stockrom.zip>
Wait for few minutes to install and boot. Report back if found any error in cmd. I have other method too.
---------- Post added at 05:33 PM ---------- Previous post was at 05:29 PM ----------
Aealo said:
Hello,
my GFs phone with Lineage OS started to bootloop randomly yesterday so I have tried to reflash it witch does not worked. Everytime I have booted into recovery twrp was unable to mount storage so I found some tutorials whose suggested to change filesystem or repair it but none of them worked. As a last resort there was unlocking bootloader but now I cant unlock it after locking because I cant access system and phone is not associated with my account anymore. Is there any way to fix this? Thanks in advance
Click to expand...
Click to collapse
http://en.miui.com/thread-835254-1-1.html this is the other method. Will definitely work
Thanks for your guide but I dont think it would work since there in no recovery in the phone, only fastboot is available. I will try EDL mode
Aealo said:
Thanks for your guide but I dont think it would work since there in no recovery in the phone, only fastboot is available. I will try EDL mode
Click to expand...
Click to collapse
You don't need unlocked bootloader for flashing stock ROM through Mi Flash Tool. If you get errors, change the cable, change the PC/Laptop, use an Intel machine instead of AMD Ryzen, use USB 2.0 port instead of 3.0 port etc.
So I have tried EDL mode but that gives me error that my account is not authorized and also normal flash on different PC and that says that I cannot erase while in LOCK state
here youtube video on edl flashing with err
might work give try
https://www.youtube.com/watch?v=p0O2PqUnem8
berty321 said:
here youtube video on edl flashing with err
might work give try
https://www.youtube.com/watch?v=p0O2PqUnem8
Click to expand...
Click to collapse
Thanks for the advice but its too late
Already got it flashed for 10eur by someone with EDL authorized account
Aealo said:
So I have tried EDL mode but that gives me error that my account is not authorized and also normal flash on different PC and that says that I cannot erase while in LOCK state
Click to expand...
Click to collapse
try to flash it with adb
Aealo said:
Thanks for the advice but its too late
Already got it flashed for 10eur by someone with EDL authorized account
Click to expand...
Click to collapse
can you teach me how did you do that? were same problem
Aealo said:
Thanks for the advice but its too late
Already got it flashed for 10eur by someone with EDL authorized account
Click to expand...
Click to collapse
Need help... Same problem "System destroyed with locked bootloader"
Aealo said:
Hello,
my GFs phone with Lineage OS started to bootloop randomly yesterday so I have tried to reflash it witch does not worked. Everytime I have booted into recovery twrp was unable to mount storage so I found some tutorials whose suggested to change filesystem or repair it but none of them worked. As a last resort there was unlocking bootloader but now I cant unlock it after locking because I cant access system and phone is not associated with my account anymore. Is there any way to fix this? Thanks in advanchi9
Aealo said:
Hello,
my GFs phone with Lineage OS started to bootloop randomly yesterday so I have tried to reflash it witch does not worked. Everytime I have booted into recovery twrp was unable to mount storage so I found some tutorials whose suggested to change filesystem or repair it but none of them worked. As a last resort there was unlocking bootloader but now I cant unlock it after locking because I cant access system and phone is not associated with my account anymore. Is there any way to fix this? Thanks in advance
Click to expand...
Click to collapse
Hi buddy can you give me the contact of your friend whose helped you with the EDL authorized account because I have same problem with my phone
Click to expand...
Click to collapse
hi, sorry I dont remember who flashed my phone but you can definitelly find someone using google. there are many telegram channels for that